Triple
T16477888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ai |
E400234
|
entity |
| Predicate | describedRelativeLocation |
P7317
|
FINISHED |
| Object | near Bethel |
—
|
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: near Bethel | Statement: [Ai, describedRelativeLocation, near Bethel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedRelativeLocation Context triple: [Ai, describedRelativeLocation, near Bethel]
-
A.
positionDescribed
Indicates that a position, location, or spatial arrangement of an entity is explicitly specified or characterized, typically in descriptive terms.
-
B.
hasRelativeLocation
chosen
Indicates that one entity is positioned in space in relation to another entity’s location.
-
C.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
D.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
E.
directionRelativeTo
Indicates the spatial orientation of one entity in relation to another, such as which way it faces or points relative to a reference entity.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e0013ac8190b607d5f47d17c501 |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:13 a.m.