Triple
T37324065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alleluia (Randall Thompson) |
E926554
|
entity |
| Predicate | primaryWord |
P26489
|
FINISHED |
| Object | Alleluia |
E926554
|
NE 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: Alleluia | Statement: [Alleluia (Randall Thompson), primaryWord, Alleluia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWord Context triple: [Alleluia (Randall Thompson), primaryWord, Alleluia]
-
A.
firstWord
chosen
Indicates that one entity is the first word in the sequence or text associated with another entity.
-
B.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
C.
principalPart
Indicates that one entity is the primary or most important component, role, or participant within the context defined by the other entity.
-
D.
primarySingle
Indicates that an entity has exactly one main or primary association of the specified type, with no additional concurrent primary associations.
-
E.
primaryName
Indicates that the associated name is the main or most commonly used name for the entity in question.
- F. None of above.
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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40639d4fcc819082820f5938e1ea8b |
completed | June 27, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.