Triple
T32555285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Hone Ropata |
E832080
|
entity |
| Predicate | professionInNarrative |
P150357
|
FINISHED |
| Object | surgeon |
—
|
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: surgeon | Statement: [Dr. Hone Ropata, professionInNarrative, surgeon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: professionInNarrative Context triple: [Dr. Hone Ropata, professionInNarrative, surgeon]
-
A.
hasProfessionInNarrative
chosen
Indicates that an entity holds or is assigned a particular profession or occupational role within the context of a narrative or story.
-
B.
occupationAsPersona
Indicates that an entity holds or performs a particular occupation specifically in the role or persona of another characterized identity.
-
C.
portraysProfession
Indicates that one entity depicts or represents another entity in a specific profession or occupational role.
-
D.
fictionalOccupation
Indicates that one entity is the imaginary or narrative-based job, role, or profession attributed to another entity within a fictional context.
-
E.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
- 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:03 a.m.