Triple
T22124159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Jones |
E546748
|
entity |
| Predicate | hasOwnerStructure |
P147083
|
FINISHED |
| Object | employee-owned partnership |
—
|
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: employee-owned partnership | Statement: [Peter Jones, hasOwnerStructure, employee-owned partnership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnerStructure Context triple: [Peter Jones, hasOwnerStructure, employee-owned partnership]
-
A.
doesNotHaveOwnershipStructure
Indicates that an entity lacks any defined or recognized ownership structure linking it to owners or controlling parties.
-
B.
hasAccessStructure
Indicates that one entity is associated with, or governed by, a particular access structure that defines the conditions or rules under which access is granted.
-
C.
hasInfrastructureOwner
Indicates that one entity owns or is responsible for the infrastructure associated with another entity.
-
D.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
E.
hasInfrastructureOwnerType
Indicates the type or category of entity that owns or is responsible for a given piece of infrastructure.
- F. None of above. chosen
Provenance (4 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1298016e081909d00015ca516d9fd |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:31 p.m.