Triple
T4078035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-57 |
E87410
|
entity |
| Predicate | geospatialType |
P35055
|
FINISHED |
| Object | vector data |
—
|
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: vector data | Statement: [S-57, geospatialType, vector data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geospatialType Context triple: [S-57, geospatialType, vector data]
-
A.
spatialProperty
Indicates a relationship where one entity has a specific spatial characteristic, such as position, size, orientation, or geometric configuration in space, relative to a reference frame or other entities.
-
B.
hasCoordinatesType
Indicates that an entity is associated with a specific type or system of coordinates used to define its position.
-
C.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
D.
geographicalRepresentation
chosen
Indicates that one entity serves as a geographic depiction, model, or mapping of another entity’s location, area, or spatial characteristics.
-
E.
spatialRelation
Indicates a spatial relationship between entities, specifying how one is positioned or located relative to another in space.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4d348c8190a94724639830aca0 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.