Triple
T37354188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonathan Scott as contractor |
E927408
|
entity |
| Predicate | occupationInRole |
P182791
|
FINISHED |
| Object | contractor |
—
|
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: contractor | Statement: [Jonathan Scott as contractor, occupationInRole, contractor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationInRole Context triple: [Jonathan Scott as contractor, occupationInRole, contractor]
-
A.
employedRole
Indicates that an entity holds or performs a specific role or position within an employment or work context.
-
B.
roleDuringOccupation
Indicates the specific role or position an entity held during a particular occupation or period of control.
-
C.
roleOfPerson
chosen
Indicates that a specific role, function, or position is assigned to or held by a particular person.
-
D.
occupationDuringAlias
Indicates that an entity held a particular occupation specifically during the time period when it was known by a given alias.
-
E.
sectorEmploymentRole
Indicates the specific role or function an entity holds within a particular employment sector or industry.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.