Triple
T36616226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapInfo TAB |
E903609
|
entity |
| Predicate | supportsThematicMapping |
P204965
|
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, supportsThematicMapping, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsThematicMapping Context triple: [MapInfo TAB, supportsThematicMapping, true]
-
A.
supportsThemingFormat
Indicates that an entity is compatible with and can correctly handle a particular theming format or style specification.
-
B.
supportsThemingSystem
Indicates that an entity is compatible with and can operate using a theming system for customizable appearance or style.
-
C.
supportsThemeOf
Indicates that one entity reinforces, aligns with, or contributes to the central theme expressed by another entity.
-
D.
hasThematicTransformation
Indicates that something undergoes a significant change or development in its central theme or thematic content over time or across contexts.
-
E.
isThemedTo
Indicates that one entity is designed, styled, or conceptually based around the subject, motif, or theme represented by another entity.
- F. None of above. chosen
Provenance (4 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.