Triple
T18796018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linde Air Products Company |
E459635
|
entity |
| Predicate | operatedFacilityType |
P121503
|
FINISHED |
| Object | air separation plant |
—
|
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 separation plant | Statement: [Linde Air Products Company, operatedFacilityType, air separation plant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedFacilityType Context triple: [Linde Air Products Company, operatedFacilityType, air separation plant]
-
A.
fccFacilityType
Indicates the specific type or classification of a facility as defined by the FCC (Federal Communications Commission).
-
B.
operatesFacility
Indicates that an entity is responsible for running, managing, or controlling the operations of a particular facility.
-
C.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
D.
operatedPlantType
chosen
Indicates that an entity operates or manages a plant (facility) of a specified type.
-
E.
productionFacilityType
Indicates the specific kind or category of facility where production or manufacturing activities take place.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a01ed3c08190890d9518ed69fdee |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.