Triple
T36817771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ash Mountains |
E909792
|
entity |
| Predicate | togetherEnclose |
P164210
|
FINISHED |
| Object | Mordor |
—
|
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: Mordor | Statement: [Ash Mountains, togetherEnclose, Mordor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: togetherEnclose Context triple: [Ash Mountains, togetherEnclose, Mordor]
-
A.
helpsEnclose
chosen
Indicates that one entity contributes to surrounding, containing, or closing off another entity, aiding in its enclosure.
-
B.
heldTogetherWith
Indicates that two or more entities are physically joined or kept in contact by some binding, fastening, or cohesive force.
-
C.
formedTogetherWith
Indicates that two or more entities were created, established, or brought into existence at the same time or as part of the same formation process.
-
D.
actedTogetherWith
Indicates that two entities participated in the same performance or production, collaborating or appearing together in an acting context.
-
E.
pullsTogetherWith
Indicates that one entity exerts force or effort jointly with another to draw or move something toward a common point or direction.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca9591e48190a5a5bdb5d72ae4b3 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.