Triple
T32221852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Clear, Alabama |
E823087
|
entity |
| Predicate | locatedAcrossBodyOfWaterFrom |
P65230
|
FINISHED |
| Object | Mobile, Alabama |
E34031
|
NE 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: Mobile, Alabama | Statement: [Point Clear, Alabama, locatedAcrossBodyOfWaterFrom, Mobile, Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAcrossBodyOfWaterFrom Context triple: [Point Clear, Alabama, locatedAcrossBodyOfWaterFrom, Mobile, Alabama]
-
A.
locatedInBodyOfWater
Indicates that an entity is situated within or on the surface of a specific body of water.
-
B.
separatedFromByWaterBody
Indicates that two entities are apart from each other with a body of water lying between them as the separating barrier.
-
C.
adjacentToBodyOfWater
Indicates that one entity is directly next to or bordering a body of water, such as a lake, river, or ocean.
-
D.
bodyOfWaterOnOtherSide
chosen
Indicates that one entity is located across a body of water from the other entity, with the water lying between them.
-
E.
locatedInBodyOfWaterSharedBy
Indicates that an entity is situated within a body of water that is shared by another specified entity.
- F. None of above.
Provenance (4 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0226c8b2f881909de3c1a5ba40fc49 |
completed | May 11, 2026, 6:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f3ba19d808190b6fbe06ef79e84e9 |
completed | June 14, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_6a0225602acc8190978ab4aacc615b8d |
completed | May 11, 2026, 6:52 p.m. |
Created at: May 1, 2026, 12:38 a.m.