Triple
T36554886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helcaraxë |
E901675
|
entity |
| Predicate | formedBoundaryBetween |
P106287
|
FINISHED |
| Object | Aman and 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: Aman and Middle-earth | Statement: [Helcaraxë, formedBoundaryBetween, Aman and Middle-earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedBoundaryBetween Context triple: [Helcaraxë, formedBoundaryBetween, Aman and Middle-earth]
-
A.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
B.
stateBoundaryBetween
Indicates a boundary line that separates or lies between two states.
-
C.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
D.
borderDefinedBetween
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
E.
laterFormedBorderBetween
chosen
Indicates that the relationship or boundary between two entities was established at a later time, forming a border between them after an earlier period or state.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00a602b6b48190a9dea8ae22d2fa05 |
completed | May 10, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_6a00a559bf3881909a7b50776d8f47bb |
completed | May 10, 2026, 3:33 p.m. |
Created at: May 3, 2026, 4:11 p.m.