Triple
T7801057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Offshore Combat Force |
E180431
|
entity |
| Predicate | roleInPeacetime |
P7158
|
FINISHED |
| Object | presence operations |
—
|
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: presence operations | Statement: [Offshore Combat Force, roleInPeacetime, presence operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPeacetime Context triple: [Offshore Combat Force, roleInPeacetime, presence operations]
-
A.
peacetimeRole
chosen
Indicates the role, function, or duties an entity holds during periods of peace rather than during wartime or conflict.
-
B.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
roleInRepublic
Indicates that an entity holds or plays a specific role or function within a republic or republican system.
-
D.
politicalOrSocialRole
Indicates that an entity holds or is associated with a specific political or social position, function, or status within a group or society.
-
E.
servedInRole
Indicates that one entity performed duties or held a position within a specified role or office in relation to another entity.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:33 p.m.