Triple
T33094309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTV Steel |
E846868
|
entity |
| Predicate | ownedFacilityIn |
P8074
|
FINISHED |
| Object | Cleveland, Ohio |
—
|
NE NERFINISHED |
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: Cleveland, Ohio | Statement: [LTV Steel, ownedFacilityIn, Cleveland, Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownedFacilityIn Context triple: [LTV Steel, ownedFacilityIn, Cleveland, Ohio]
-
A.
ownsFacilityOn
chosen
Indicates that one entity possesses ownership or control over a facility located on or associated with another entity (such as a site, property, or area).
-
B.
locatedInBuildingOwnedBy
Indicates that one entity is situated within a building that is owned by another entity.
-
C.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
-
D.
usesFacilityFor
Indicates that an entity makes use of a particular facility to carry out a specific purpose, activity, or function.
-
E.
ownershipBasedIn
Indicates that an entity’s ownership or controlling stake is primarily located, registered, or based in a particular place or jurisdiction.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a7c6348190bc2f40bdf6597288 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.