Triple
T19161111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas City Plant |
E469054
|
entity |
| Predicate | locatedInFacilityType |
P37657
|
FINISHED |
| Object | industrial complex |
—
|
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: industrial complex | Statement: [Kansas City Plant, locatedInFacilityType, industrial complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFacilityType Context triple: [Kansas City Plant, locatedInFacilityType, industrial complex]
-
A.
usedAtFacilityType
Indicates that something is utilized or applied within a facility of a specified type.
-
B.
isWithinFacility
chosen
Indicates that one entity is physically located inside the boundaries or premises of a specified facility.
-
C.
locationOfFacility
Indicates that a facility is situated at or associated with a specific geographic location.
-
D.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
E.
basedOnFacility
Indicates that something is determined, derived, or decided according to the characteristics, rules, or conditions of a particular facility.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eebd093c81909a50f1119e284069 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.