Triple
T21482080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Jones |
E530017
|
entity |
| Predicate | previouslyWorkedAs |
P107616
|
FINISHED |
| Object | head chef in Paris |
—
|
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: head chef in Paris | Statement: [Adam Jones, previouslyWorkedAs, head chef in Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyWorkedAs Context triple: [Adam Jones, previouslyWorkedAs, head chef in Paris]
-
A.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
B.
earlierOccupation
Indicates that one occupation held by an entity occurred before another occupation in that entity’s work history.
-
C.
hasPastOccupation
chosen
Indicates that an entity previously held a particular job, role, or occupation in the past.
-
D.
initiallyWorksFor
Indicates that an entity’s first or original employment or working relationship is with a specified organization or employer.
-
E.
hasWorkedIn
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea338f988190a3044f8d02a567fe |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:21 p.m.