Triple
T23876882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messiah |
E592890
|
entity |
| Predicate | keyMovementsInclude |
P154290
|
FINISHED |
| Object | For unto us a Child is born |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: For unto us a Child is born | Statement: [Messiah, keyMovementsInclude, For unto us a Child is born]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyMovementsInclude Context triple: [Messiah, keyMovementsInclude, For unto us a Child is born]
-
A.
keyMovement
Indicates the movement or transfer of a key from one location, state, or holder to another.
-
B.
hasKeyMovement
Indicates that one entity possesses or defines the primary or characteristic movement pattern associated with another entity.
-
C.
keyMovementsKnownFor
Indicates that an entity is recognized for specific significant movements, actions, or stylistic developments associated with it.
-
D.
keyAction
Indicates an action that is performed using a key, typically involving locking, unlocking, or otherwise operating a mechanism that requires a key.
-
E.
keyHitter
Indicates that an entity is a powerful or highly effective performer, especially in a competitive or performance-based context.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cc02277c8190b0c15d6525f3b38d |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:15 p.m.