Triple
T28609479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NetWare |
E724135
|
entity |
| Predicate | companyHeadquartersDuringDevelopment |
P33964
|
FINISHED |
| Object | Provo, Utah |
—
|
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: Provo, Utah | Statement: [NetWare, companyHeadquartersDuringDevelopment, Provo, Utah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyHeadquartersDuringDevelopment Context triple: [NetWare, companyHeadquartersDuringDevelopment, Provo, Utah]
-
A.
companyHeadquartersLocationAtIntroduction
Indicates the location of a company’s headquarters at the time it was first introduced or came into existence.
-
B.
placeOfDevelopment
chosen
Indicates the location where something (such as a product, project, or work) was created, designed, or developed.
-
C.
headquartersLocationOfFoundedCompany
Indicates that a specific place serves as the headquarters location of a company that was founded there.
-
D.
laterCompanyHeadquartersCity
Indicates that the specified city is the location of a company’s headquarters during a later period in time, following an earlier headquarters location.
-
E.
headquartersFoundedAt
Indicates that an organization's headquarters was originally established at a specific location.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 4:29 a.m.