Triple
T36616220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MapInfo TAB |
E903609
|
entity |
| Predicate | primaryIndexFile |
P29007
|
FINISHED |
| Object | .id |
—
|
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: .id | Statement: [MapInfo TAB, primaryIndexFile, .id]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryIndexFile Context triple: [MapInfo TAB, primaryIndexFile, .id]
-
A.
primaryIndex
Indicates that one entity serves as the main or default index used to organize, access, or reference another entity within a system or dataset.
-
B.
primaryFile
chosen
Indicates that one file in a set is designated as the main or most important file associated with a given entity or context.
-
C.
indexDataFile
Indicates the action of creating or updating an index for a data file so its contents can be efficiently searched or accessed.
-
D.
primaryDatabase
Indicates that one database serves as the main or authoritative data source in relation to another system or database.
-
E.
coreIndex
Indicates the position or identifier of an entity within a central or primary ordered structure (its core sequence or index).
- 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.