Triple
T10425878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSI |
E245783
|
entity |
| Predicate | modeCoverage |
P37435
|
FINISHED |
| Object | air transportation |
—
|
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: air transportation | Statement: [TSI, modeCoverage, air transportation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeCoverage Context triple: [TSI, modeCoverage, air transportation]
-
A.
coverageModel
Indicates a relationship where a specific model or framework defines, structures, or governs the extent and manner in which something is covered or addressed.
-
B.
componentCoverage
Indicates that one entity provides coverage, protection, or support for another as one of its components or constituent parts.
-
C.
formatCoverage
Indicates how thoroughly or extensively a particular format or formatting scheme is applied or supported in a given context.
-
D.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
E.
coversMode
chosen
Indicates that one entity includes, addresses, or supports a particular mode or manner of operation associated with another entity.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea48cb348190ad4432f263300592 |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:12 p.m.