Triple
T16895252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manuel |
E424281
|
entity |
| Predicate | inUniverseWorkplaceRole |
P124907
|
FINISHED |
| Object | junior waiter |
—
|
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: junior waiter | Statement: [Manuel, inUniverseWorkplaceRole, junior waiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseWorkplaceRole Context triple: [Manuel, inUniverseWorkplaceRole, junior waiter]
-
A.
socialRoleInWork
Indicates the role or position an entity holds within a work-related or professional social context.
-
B.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
C.
inUniverseOrganization
Indicates that an organization exists and operates within a specified fictional or narrative universe.
-
D.
sectorEmploymentRole
Indicates the specific role or function an entity holds within a particular employment sector or industry.
-
E.
roleInPersonnelMatters
Indicates that one entity has a specific function, authority, or involvement in managing or deciding personnel-related matters concerning 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8d7aec88190888f13601acbcd77 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32e2c07b081908c8fee9f5507bb9e |
completed | April 18, 2026, 7:09 a.m. |
Created at: April 10, 2026, 5:29 a.m.