Triple
T17560955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoJSON |
E427694
|
entity |
| Predicate | representsCoordinatesAs |
P105386
|
FINISHED |
| Object | numeric arrays |
—
|
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: numeric arrays | Statement: [GeoJSON, representsCoordinatesAs, numeric arrays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsCoordinatesAs Context triple: [GeoJSON, representsCoordinatesAs, numeric arrays]
-
A.
usesCoordinateRepresentation
chosen
Indicates that one entity expresses or handles another entity in terms of a specific coordinate-based representation.
-
B.
representsAs
Indicates that one entity serves as a depiction, symbol, or stand-in for another entity in some representational context.
-
C.
hasCoordinates
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
-
D.
coordinatesWith
Indicates that one entity works together with another in an organized or synchronized manner to achieve a shared or compatible outcome.
-
E.
hasCoordinatesType
Indicates that an entity is associated with a specific type or system of coordinates used to define its position.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456267e208190a1238fbe1a535bb0 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.