Triple
T15713254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REI |
E380890
|
entity |
| Predicate | hasEmployeeOwnershipElement |
P119885
|
FINISHED |
| Object | profit-sharing for employees |
—
|
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: profit-sharing for employees | Statement: [REI, hasEmployeeOwnershipElement, profit-sharing for employees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmployeeOwnershipElement Context triple: [REI, hasEmployeeOwnershipElement, profit-sharing for employees]
-
A.
hasSupporterOwnershipElement
Indicates that an entity includes or is associated with an ownership-related element specifically tied to a supporter.
-
B.
hasEmployees
Indicates that one entity employs one or more other entities as its workers or staff.
-
C.
hasOwnerShare
Indicates that an entity holds a specified ownership stake or share in another entity or asset.
-
D.
hasOwnershipForm
Indicates that an entity possesses a particular legal or organizational form of ownership (such as private, public, or cooperative).
-
E.
ownsOrManages
Indicates that one entity has ownership of, or managerial control over, another entity.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f90aea0819082a9e9fe0f7780b0 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:45 a.m.