Triple
T32619710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Francis Ryan |
E833887
|
entity |
| Predicate | missionObjectiveFor |
P129227
|
FINISHED |
| Object | Captain John H. Miller |
—
|
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: Captain John H. Miller | Statement: [James Francis Ryan, missionObjectiveFor, Captain John H. Miller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionObjectiveFor Context triple: [James Francis Ryan, missionObjectiveFor, Captain John H. Miller]
-
A.
secretObjective
Indicates that an entity has a hidden or undisclosed goal or target that is not known to others.
-
B.
militaryObjectiveOf
chosen
Indicates that something serves as a military target, goal, or purpose specifically associated with a given actor or force.
-
C.
missionFirst
Indicates that one entity prioritizes accomplishing a mission or objective above other considerations or interests.
-
D.
expeditionObjective
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
E.
militaryObjectiveType
Indicates the specific category or kind of military objective that characterizes the action or relationship.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:06 a.m.