Triple
T2389223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daniel Kottke |
E48900
|
entity |
| Predicate | employedInRole |
P4325
|
FINISHED |
| Object | hardware technician at Apple |
—
|
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: hardware technician at Apple | Statement: [Daniel Kottke, employedInRole, hardware technician at Apple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedInRole Context triple: [Daniel Kottke, employedInRole, hardware technician at Apple]
-
A.
employedApproximately
Indicates that one entity employs another in a manner where the number, duration, or extent of employment is approximate rather than exact.
-
B.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
C.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
D.
workedAs
chosen
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
E.
positionInWork
Indicates the specific role, rank, or placement an entity holds within a larger work or structured composition.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc7dca9248190b634ae9e02f6899a |
completed | March 7, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.