Triple
T847699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Their Pilgrimage |
E18312
|
entity |
| Predicate | hasMainCharacters |
P8706
|
FINISHED |
| Object | two young travelers |
—
|
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: two young travelers | Statement: [Their Pilgrimage, hasMainCharacters, two young travelers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCharacters Context triple: [Their Pilgrimage, hasMainCharacters, two young travelers]
-
A.
hasProtagonist
chosen
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
C.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
hasMainSpeaker
Indicates that one entity serves as the primary or principal speaker associated with another entity, such as an event, recording, or presentation.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac1e41748190a21cd1ce5ebcb8ff |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa807adc8190ad808a573cf8e923 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.