Triple
T36616214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapInfo TAB |
E903609
|
entity |
| Predicate | supportsProjections |
P124797
|
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: [MapInfo TAB, supportsProjections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProjections Context triple: [MapInfo TAB, supportsProjections, true]
-
A.
usesProjectionMappingOn
Indicates that one entity applies projection mapping techniques onto another entity, typically by projecting images or video content onto its surface.
-
B.
hasProjectionSystem
chosen
Indicates that one entity uses or is defined by a particular coordinate or map projection system associated with another entity.
-
C.
supportsProjectsIn
Indicates that one entity provides assistance, resources, or backing for projects occurring within or associated with another entity.
-
D.
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.
-
E.
supportsAggregation
Indicates that one entity enables or allows another entity to be combined, grouped, or summarized with others through an aggregation operation.
- 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_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.