Triple
T36546899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hildórien |
E901161
|
entity |
| Predicate | worldAxisRelation |
P126238
|
FINISHED |
| Object | far East of Middle-earth |
—
|
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: far East of Middle-earth | Statement: [Hildórien, worldAxisRelation, far East of Middle-earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldAxisRelation Context triple: [Hildórien, worldAxisRelation, far East of Middle-earth]
-
A.
relationshipWithAxis
chosen
Indicates a specified way in which something is oriented, aligned, or otherwise related with respect to a particular axis.
-
B.
formsAxisOf
Indicates that one entity serves together with another as the central line or primary axis around which a structure, system, or configuration is organized.
-
C.
axisWith
Indicates that one entity serves as or lies along a principal axis in relation to another entity.
-
D.
locationOrientation
Indicates how one entity is spatially oriented or positioned relative to a specific location or reference point.
-
E.
relationshipToWorld
Indicates how an entity is connected or related to the broader world or external environment.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:11 p.m.