Triple
T36546900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hildórien |
E901161
|
entity |
| Predicate | firstMenMigratedFrom |
P185835
|
FINISHED |
| Object | Hildórien |
E901161
|
NE 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: Hildórien | Statement: [Hildórien, firstMenMigratedFrom, Hildórien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMenMigratedFrom Context triple: [Hildórien, firstMenMigratedFrom, Hildórien]
-
A.
migrationDirectionOfFirstMen
chosen
Indicates the direction in which the first men migrated or moved from their original location.
-
B.
firstPermanentSettler
Indicates that the subject is the earliest individual or group to establish a lasting, continuous residence in the location or entity specified by the object.
-
C.
cameToAmericaAs
Indicates that one entity migrated or traveled to America in the role, capacity, or status specified by the other entity.
-
D.
firstSettlersArrived
Indicates that the earliest group of settlers reached or came to a particular place or region.
-
E.
foundingAncestorMigration
Indicates the movement or relocation of an original founding ancestor from one place to another, establishing the ancestral line in the destination.
- F. None of above.
Provenance (4 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a094c29e88190b8e14c2f6d12fb8b |
completed | June 23, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.