Triple
T36269733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Antonio parish |
E892636
|
entity |
| Predicate | hasCoordinateFeature |
P204809
|
FINISHED |
| Object | 0° latitude |
—
|
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: 0° latitude | Statement: [San Antonio parish, hasCoordinateFeature, 0° latitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoordinateFeature Context triple: [San Antonio parish, hasCoordinateFeature, 0° latitude]
-
A.
hasCoordinates
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
-
B.
hasCoordinatesType
Indicates that an entity is associated with a specific type or system of coordinates used to define its position.
-
C.
hasCoordinateRole
Indicates that one entity shares an equivalent or parallel role or function with another entity within the same context or structure.
-
D.
hasCoordinateDescription
Indicates that an entity is associated with a textual or structured description of its spatial or geographic coordinates.
-
E.
hasCoordinatePrecision
Indicates the degree of exactness or granularity with which an entity’s spatial coordinates are specified.
- F. None of above. chosen
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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:09 p.m.