Triple
T4562222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Flattery |
E121818
|
entity |
| Predicate | locatedAtExtremityOf |
P27245
|
FINISHED |
| Object | contiguous United States |
—
|
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: contiguous United States | Statement: [Cape Flattery, locatedAtExtremityOf, contiguous United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtExtremityOf Context triple: [Cape Flattery, locatedAtExtremityOf, contiguous United States]
-
A.
locatedAtBaseOf
Indicates that one entity is positioned at or near the bottom or lowest supporting part of another entity.
-
B.
locatedAtTerminusOf
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
-
C.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
D.
locatedAtTipOf
chosen
Indicates that one entity is positioned at the extreme end or tip of another entity.
-
E.
locatedAtCornerOf
Indicates that one entity is positioned at or forms the corner where two or more boundaries, edges, or intersecting paths meet.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd582f21648190b49284eb61b618c9 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.