Triple
T24062696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rochester, New York, United States |
E595996
|
entity |
| Predicate | majorCompanyFoundedThere |
P23300
|
FINISHED |
| Object | Eastman Kodak Company |
—
|
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: Eastman Kodak Company | Statement: [Rochester, New York, United States, majorCompanyFoundedThere, Eastman Kodak Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCompanyFoundedThere Context triple: [Rochester, New York, United States, majorCompanyFoundedThere, Eastman Kodak Company]
-
A.
headquartersFoundedCompanyIn
Indicates that a headquarters entity established or founded a particular company.
-
B.
notableCompanyFoundedIn
chosen
Indicates that a company is recognized as notable and was founded in the specified location or time period.
-
C.
foundedCompany
Indicates that an entity established or created a company, typically as its founder or co-founder.
-
D.
majorCompanyLocatedIn
Indicates that a major company has its primary presence or headquarters in a specified location.
-
E.
foundingCompany
Indicates that one entity is the company that established or created another entity (such as an organization, project, or subsidiary).
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da5825548190b94cb6e708617a7d |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:38 p.m.