Triple
T29304933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles Boardman |
E743065
|
entity |
| Predicate | missionInvolves |
P73456
|
FINISHED |
| Object | Richard Muller |
—
|
NE NERFINISHED |
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: Richard Muller | Statement: [Charles Boardman, missionInvolves, Richard Muller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionInvolves Context triple: [Charles Boardman, missionInvolves, Richard Muller]
-
A.
missionTo
chosen
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
-
B.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of another entity.
-
C.
missionField
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.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
E.
missionFirst
Indicates that one entity prioritizes accomplishing a mission or objective above other considerations or interests.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 1:12 p.m.