Triple
T36616222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapInfo TAB |
E903609
|
entity |
| Predicate | geometryDataFile |
P135883
|
FINISHED |
| Object | .map |
—
|
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: .map | Statement: [MapInfo TAB, geometryDataFile, .map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geometryDataFile Context triple: [MapInfo TAB, geometryDataFile, .map]
-
A.
geometricFeature
Indicates a relationship where one entity possesses or is characterized by a specific geometric property, shape, or structural feature.
-
B.
testGeometry
Indicates that an entity is involved in evaluating, validating, or analyzing geometric properties, shapes, or spatial relationships.
-
C.
storesGeometryIn
chosen
Indicates that one entity holds or contains the geometric representation or spatial data of another entity.
-
D.
geometricSetting
Indicates the spatial or geometric context within which an object, relation, or event is defined or occurs.
-
E.
spatialElements
Indicates a relationship where one or more elements are associated through their positions, arrangement, or relationships within a physical or conceptual 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.