Triple
T27618865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O Come All Ye Faithful |
E700514
|
entity |
| Predicate | firstLineEnglish |
P197547
|
FINISHED |
| Object | O come, all ye faithful, joyful and triumphant |
—
|
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: O come, all ye faithful, joyful and triumphant | Statement: [O Come All Ye Faithful, firstLineEnglish, O come, all ye faithful, joyful and triumphant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLineEnglish Context triple: [O Come All Ye Faithful, firstLineEnglish, O come, all ye faithful, joyful and triumphant]
-
A.
firstLineTranslation
Indicates that one text is a translation of the first line of another text.
-
B.
firstLines
chosen
Indicates that one text, segment, or element constitutes the initial lines or opening portion of another.
-
C.
firstLineAfrikaans
Indicates that the specified text is the first line of a piece of content when written in Afrikaans.
-
D.
firstWord
Indicates that one entity is the first word in the sequence or text associated with another entity.
-
E.
firstLineForm
Indicates that one entity is the initial or primary line-based representation or form of another entity.
- F. None of above.
Provenance (3 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: April 27, 2026, 2:13 p.m.