Triple
T31056659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIR 2004 |
E791414
|
entity |
| Predicate | informationTypeCovered |
P66881
|
FINISHED |
| Object | air |
—
|
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 | Statement: [EIR 2004, informationTypeCovered, air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationTypeCovered Context triple: [EIR 2004, informationTypeCovered, air]
-
A.
informationTypeHandled
Indicates that an entity is responsible for processing, managing, or dealing with a particular type or category of information.
-
B.
typeOfInformation
chosen
Indicates that one entity specifies the category or kind of information that characterizes or describes another entity.
-
C.
coversDisclosureOf
Indicates that one entity’s scope, terms, or provisions include and apply to the act or content of another entity’s disclosure.
-
D.
securityTypeCoverage
Indicates the type or category of security that is covered or included under a given coverage or policy.
-
E.
categoryCovered
Indicates that one category is included within, addressed by, or encompassed under the scope of another entity or context.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9 p.m.