Triple
T29530851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nacotchtanke |
E749196
|
entity |
| Predicate | areaNowWithin |
P39182
|
FINISHED |
| Object | District of Columbia |
—
|
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: District of Columbia | Statement: [Nacotchtanke, areaNowWithin, District of Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaNowWithin Context triple: [Nacotchtanke, areaNowWithin, District of Columbia]
-
A.
isInArea
chosen
Indicates that one entity is located within the spatial bounds or region defined by another entity.
-
B.
regionContains
Indicates that one region spatially encompasses or includes another region within its boundaries.
-
C.
existsWithin
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
D.
notableAreaWithin
Indicates that one area is a particularly significant or noteworthy part located inside another, larger area.
-
E.
enclosesArea
Indicates that one entity surrounds and contains a bounded region of space occupied or defined by another.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cc2656081908adb6f119caa0cc1 |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:52 p.m.