Triple
T28890502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easterlings |
E732680
|
entity |
| Predicate | firstMenToArriveInBeleriandComparedTo |
P167152
|
FINISHED |
| Object | Edain (later than Edain) |
—
|
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: Edain (later than Edain) | Statement: [Easterlings, firstMenToArriveInBeleriandComparedTo, Edain (later than Edain)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMenToArriveInBeleriandComparedTo Context triple: [Easterlings, firstMenToArriveInBeleriandComparedTo, Edain (later than Edain)]
-
A.
timeOfArrivalInArda
Indicates the point in time at which an entity arrives in Arda.
-
B.
enteredBeleriand
Indicates that an entity moved into or came within the region or realm referred to as Beleriand.
-
C.
amongFirstToReach
chosen
Indicates that an entity is one of the earliest individuals or groups to arrive at, achieve, or attain a particular place, state, or milestone.
-
D.
ElrondChose
Indicates that Elrond made a deliberate selection or decision regarding a particular option, entity, or course of action.
-
E.
firstCrewBoarded
Indicates that the initial group of crew members has boarded or entered a specified vehicle, vessel, or location.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
Created at: April 28, 2026, 7:54 a.m.