Triple
T17799134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Winslow |
E444373
|
entity |
| Predicate | postActingOccupation |
P128960
|
FINISHED |
| Object | postal worker |
—
|
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: postal worker | Statement: [George Winslow, postActingOccupation, postal worker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postActingOccupation Context triple: [George Winslow, postActingOccupation, postal worker]
-
A.
postPlayingRole
Indicates that an entity assumes or holds a particular role after a playing or performance event has taken place.
-
B.
employedActor
Indicates that one entity has hired or currently employs another entity to perform work or services.
-
C.
portraysProfession
Indicates that one entity depicts or represents another entity in a specific profession or occupational role.
-
D.
portrayedByProfession
Indicates that an entity is depicted or represented by someone acting in a specified professional capacity.
-
E.
namedAfterOccupationOrRole
Indicates that an entity is named after a specific occupation, profession, or social role associated with a person or group.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487fe19dc8190b7e9dc96f39e0861 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:13 a.m.