Triple
T2231019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PIT |
E48763
|
entity |
| Predicate | usedInDataFormats |
P5027
|
FINISHED |
| Object | CSV stats exports |
—
|
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: CSV stats exports | Statement: [PIT, usedInDataFormats, CSV stats exports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDataFormats Context triple: [PIT, usedInDataFormats, CSV stats exports]
-
A.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
B.
usedInMachineReadableContexts
chosen
Indicates that something is employed or applied within formats or environments that can be automatically processed and interpreted by machines.
-
C.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
D.
usedInProtocol
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
-
E.
usedInDigitalMedia
Indicates that something is employed, featured, or incorporated within digital media content or platforms.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc06b7374819089fe643e12797bfd |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.