Triple
T3216654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paolo Giordano |
E67412
|
entity |
| Predicate | hasOccupationChange |
P28984
|
FINISHED |
| Object | physicist-turned-novelist |
—
|
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: physicist-turned-novelist | Statement: [Paolo Giordano, hasOccupationChange, physicist-turned-novelist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccupationChange Context triple: [Paolo Giordano, hasOccupationChange, physicist-turned-novelist]
-
A.
hadOccupationStatusUntil
Indicates that an entity held a particular occupational status up to, but not necessarily beyond, a specified point in time.
-
B.
earlierOccupation
chosen
Indicates that one occupation held by an entity occurred before another occupation in that entity’s work history.
-
C.
hasMajorEmployerHistory
Indicates that an entity has a documented history of employment with a major or significant employer.
-
D.
hasWorkedIn
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
E.
hasWorkedFor
Indicates that an entity has been employed by or has provided work or services to another entity.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab096b588190b22e41a76263ae92 |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.