Triple
T6747894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Loop |
E154263
|
entity |
| Predicate | outerBoundaryFor |
P71578
|
FINISHED |
| Object | many Washington, D.C. suburbs |
—
|
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: many Washington, D.C. suburbs | Statement: [Inner Loop, outerBoundaryFor, many Washington, D.C. suburbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outerBoundaryFor Context triple: [Inner Loop, outerBoundaryFor, many Washington, D.C. suburbs]
-
A.
hasOuterBoundaryRadius
Indicates that an entity has an outer boundary characterized by a specific radius measurement.
-
B.
isBoundaryFor
chosen
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
C.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
D.
innerBoundaryRegion
Indicates that one region serves as the inner boundary or enclosed area within another region or geometric entity.
-
E.
hasUncertainOuterBoundary
Indicates that the outer boundary of an entity is not precisely defined, fixed, or clearly determined.
- 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_69c6880ef37881909268a5a7299b9293 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:11 p.m.