Triple
T16705460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ORLY |
E405955
|
entity |
| Predicate | hasUnderlyingCompanyFoundedInYear |
P15704
|
FINISHED |
| Object | 1957 |
—
|
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: 1957 | Statement: [ORLY, hasUnderlyingCompanyFoundedInYear, 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnderlyingCompanyFoundedInYear Context triple: [ORLY, hasUnderlyingCompanyFoundedInYear, 1957]
-
A.
underlyingFoundedBy
Indicates that an entity’s foundational creation or establishment is ultimately attributable to another entity, which serves as its underlying founder.
-
B.
associatedCompanyFoundedIn
chosen
Indicates that the related company was founded in the specified year or time period.
-
C.
hasUnderlyingCompanyIPOApproxYear
Indicates the approximate calendar year in which the underlying company completed its initial public offering (IPO).
-
D.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
E.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e383355f908190be467a12079b3d6f |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.