Triple
T35470320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veronica Dare |
E1025189
|
entity |
| Predicate | primaryObjectiveInHalo3ODST |
P206997
|
FINISHED |
| Object | secure ONI asset in New Mombasa |
—
|
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: secure ONI asset in New Mombasa | Statement: [Veronica Dare, primaryObjectiveInHalo3ODST, secure ONI asset in New Mombasa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryObjectiveInHalo3ODST Context triple: [Veronica Dare, primaryObjectiveInHalo3ODST, secure ONI asset in New Mombasa]
-
A.
roverPrimaryObjective
Indicates that the specified objective is the main or primary mission goal assigned to the rover.
-
B.
secretObjective
Indicates that an entity has a hidden or undisclosed goal or target that is not known to others.
-
C.
insurgentObjective
Indicates that an insurgent group or actor has a specific strategic goal, target, or desired outcome they are attempting to achieve.
-
D.
primaryAlliedObjective
Indicates the main goal or target that allied entities are jointly striving to achieve.
-
E.
militaryObjectiveType
Indicates the specific category or kind of military objective that characterizes the action or relationship.
- F. None of above. chosen
Provenance (4 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.