Triple
T36723585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgul Vale |
E907133
|
entity |
| Predicate | formerlyApproachTo |
P202687
|
FINISHED |
| Object | Minas Ithil |
—
|
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: Minas Ithil | Statement: [Morgul Vale, formerlyApproachTo, Minas Ithil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyApproachTo Context triple: [Morgul Vale, formerlyApproachTo, Minas Ithil]
-
A.
usedToApproach
Indicates that one entity employed another entity as a means or method to move closer to or reach a target entity or location.
-
B.
approaches
Indicates that one entity moves closer in position or state to another entity or reference point.
-
C.
guardedApproachTo
Indicates a cautious, defensive, or wary manner of moving toward or engaging with another entity.
-
D.
formsApproachTo
Indicates that one entity develops or establishes a particular method, strategy, or way of dealing with or addressing another entity or situation.
-
E.
approche
Indicates that one entity moves or positions itself closer to another entity or reference point.
- F. None of above. chosen
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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_6a00acf7923c819091ae7fbda05164f6 |
completed | May 10, 2026, 4:06 p.m. |
Created at: May 3, 2026, 4:12 p.m.