Triple
T32224603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alatar |
E823160
|
entity |
| Predicate | cameTo |
P2694
|
FINISHED |
| Object | Middle-earth |
—
|
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: Middle-earth | Statement: [Alatar, cameTo, Middle-earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameTo Context triple: [Alatar, cameTo, Middle-earth]
-
A.
wentTo
chosen
Indicates that one entity traveled or moved from its original location to another specified place.
-
B.
broughtTo
Indicates that one entity caused another entity or object to be transported or accompanied to a particular destination or recipient.
-
C.
cameToPowerThrough
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
D.
carriedTo
Indicates that one entity transported or conveyed another entity from one place to another.
-
E.
broughtOn
Indicates that one entity caused, initiated, or was responsible for the occurrence or introduction of another entity or event.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbc8c6c881908ce99e774c010ff5 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:38 a.m.