Triple
T34639823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teleri |
E889525
|
entity |
| Predicate | followedOnGreatJourney |
P196255
|
FINISHED |
| Object | Oromë |
—
|
NE NERFINISHED |
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: Oromë | Statement: [Teleri, followedOnGreatJourney, Oromë]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedOnGreatJourney Context triple: [Teleri, followedOnGreatJourney, Oromë]
-
A.
followedOnPilgrimageBy
Indicates that one entity was accompanied or succeeded by another entity during a pilgrimage journey.
-
B.
followsTour
Indicates that one entity attends or participates in a tour that occurs after, or as a consequence of, another specified event or tour.
-
C.
followsExpeditionTo
chosen
Indicates that one entity accompanies or trails another entity on an expedition or journey to a particular destination.
-
D.
precededOnPilgrimageBy
Indicates that one entity went on a pilgrimage earlier in time than another, such that the first entity’s pilgrimage occurred before the second’s.
-
E.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: May 1, 2026, 2:04 a.m.