Triple
T8493510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Michaels |
E201033
|
entity |
| Predicate | missionContext |
P33202
|
FINISHED |
| Object | medical procedure inside a human body |
—
|
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: medical procedure inside a human body | Statement: [Dr. Michaels, missionContext, medical procedure inside a human body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionContext Context triple: [Dr. Michaels, missionContext, medical procedure inside a human body]
-
A.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
B.
missionScope
Indicates the defined range, objectives, and boundaries within which a mission or operation is intended to be carried out.
-
C.
missionField
chosen
Indicates a relationship where an entity’s work, activity, or purpose is directed toward a particular area, domain, or target context as its mission focus.
-
D.
missionLed
Indicates that an entity served as the leader or commander of a particular mission.
-
E.
missionFocus
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe579b7088190b297b04527e36a2b |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.