Triple
T12917014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viktor Navorski |
E309010
|
entity |
| Predicate | laterOccupationInAirport |
P75487
|
FINISHED |
| Object | construction 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: construction worker | Statement: [Viktor Navorski, laterOccupationInAirport, construction worker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterOccupationInAirport Context triple: [Viktor Navorski, laterOccupationInAirport, construction worker]
-
A.
memberLaterOccupation
chosen
Indicates that an individual later held a particular occupation or position after an earlier point in time or role.
-
B.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
C.
airportRole
Indicates that an entity serves a specific functional role or capacity within the context of an airport.
-
D.
laterOffice
Indicates that one office or term of office occurs chronologically after another office or term.
-
E.
laterWorksAt
Indicates that an entity begins working at a place or organization at a time later than another referenced time or employment situation.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971a1e8088190af697629baecf59f |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.