Triple
T2370486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NKE |
E46076
|
entity |
| Predicate | hasUnderlyingCompanyFoundedYear |
P15704
|
FINISHED |
| Object | 1964 |
—
|
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: 1964 | Statement: [NKE, hasUnderlyingCompanyFoundedYear, 1964]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingCompanyFoundedYear Context triple: [NKE, hasUnderlyingCompanyFoundedYear, 1964]
-
A.
associatedCompanyFoundedIn
chosen
Indicates that the related company was founded in the specified year or time period.
-
B.
underlyingFoundedBy
Indicates that an entity’s foundational creation or establishment is ultimately attributable to another entity, which serves as its underlying founder.
-
C.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
D.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
-
E.
foundedInYearApprox
Indicates that an entity was established or came into existence around an approximate year, rather than on a precisely known date.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abc76f5aec8190867d621e6849258c |
completed | March 7, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69abc59b88348190a2d6c08f69974117 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.