Triple
T31886920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf Coast region (inland) |
E814031
|
entity |
| Predicate | notLocatedOn |
P52622
|
FINISHED |
| Object | immediate Gulf coastline |
—
|
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: immediate Gulf coastline | Statement: [Gulf Coast region (inland), notLocatedOn, immediate Gulf coastline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notLocatedOn Context triple: [Gulf Coast region (inland), notLocatedOn, immediate Gulf coastline]
-
A.
notLocatedAt
chosen
Indicates that an entity is explicitly not situated, present, or found at a specified location.
-
B.
locatedOff
Indicates that one entity is situated away from, but in the vicinity of, another entity or reference point, rather than directly on or within it.
-
C.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
D.
notListedOn
Indicates that an entity is absent from, or does not appear in, a specified list, registry, or catalog.
-
E.
notFoundOnIsland
Indicates that the specified entity does not exist or cannot be located on the given island.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0e999888190b9dd00c81f5df261 |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:57 p.m.