Triple
T29867408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gbXML |
E758493
|
entity |
| Predicate | supportsCoordinateSystems |
P2054
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [gbXML, supportsCoordinateSystems, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCoordinateSystems Context triple: [gbXML, supportsCoordinateSystems, true]
-
A.
supportsSRID
Indicates that one entity provides compatibility with, recognition of, or operational support for a specified Spatial Reference System Identifier (SRID) associated with another entity.
-
B.
usesCoordinateRepresentation
Indicates that one entity expresses or handles another entity in terms of a specific coordinate-based representation.
-
C.
usesCoordinateReference
Indicates that one entity adopts or relies on the coordinate reference system defined or provided by another entity.
-
D.
coordinateSystem
chosen
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
E.
hasProjectionSystem
Indicates that one entity uses or is defined by a particular coordinate or map projection system associated with another entity.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:52 p.m.