Triple
T36616224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapInfo TAB |
E903609
|
entity |
| Predicate | metadataFile |
P163534
|
FINISHED |
| Object | .tab |
—
|
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: .tab | Statement: [MapInfo TAB, metadataFile, .tab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metadataFile Context triple: [MapInfo TAB, metadataFile, .tab]
-
A.
metadataLocation
Indicates the location or source where descriptive or administrative information about an entity is stored or can be accessed.
-
B.
metadata
chosen
Indicates that one entity provides descriptive or contextual information about another entity, such as its properties, origin, or structure.
-
C.
metadataType
Indicates that one entity specifies the kind or category of metadata associated with another entity.
-
D.
metaElement
Indicates that one entity functions as a meta-level descriptor, annotation, or structural element that provides information about another entity rather than being part of its primary content.
-
E.
dynamicMetadataSupport
Indicates that the subject system or component is capable of handling metadata that can change or be updated at runtime rather than being fixed or static.
- 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.