Triple
T36817805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fangorn Forest |
E909793
|
entity |
| Predicate | easternEdgeBorders |
P20602
|
FINISHED |
| Object | Rohan |
—
|
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: Rohan | Statement: [Fangorn Forest, easternEdgeBorders, Rohan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternEdgeBorders Context triple: [Fangorn Forest, easternEdgeBorders, Rohan]
-
A.
boundaryTypeEast
Indicates the type or nature of the boundary that lies to the east of a given entity.
-
B.
easternTerminusAtBorderWith
Indicates that something’s eastern endpoint or final location lies at, or directly on, a border shared with another entity.
-
C.
easternBoundaryFormedBy
Indicates that the eastern boundary of an area, region, or object is defined or formed by a specified feature or entity.
-
D.
bordersToTheEast
chosen
Indicates that one entity shares a boundary with another entity and is located directly to the east of it.
-
E.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
- 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.