Triple
T8887060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Labuan |
E211556
|
entity |
| Predicate | objectiveAchieved |
P49791
|
FINISHED |
| Object | airstrip on Labuan restored for Allied use |
—
|
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: airstrip on Labuan restored for Allied use | Statement: [Battle of Labuan, objectiveAchieved, airstrip on Labuan restored for Allied use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveAchieved Context triple: [Battle of Labuan, objectiveAchieved, airstrip on Labuan restored for Allied use]
-
A.
achieved
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
B.
achievedOn
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
-
C.
achievementStatus
Indicates the current state or level of completion of an achievement-related goal or milestone for an entity.
-
D.
strategicAchievement
chosen
Indicates the accomplishment of a significant, high-level goal or milestone that advances an overarching strategy or long-term plan.
-
E.
notableObjective
Indicates that an entity has a significant, distinguished, or widely recognized goal, purpose, or target associated with it.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc618d4c188190810d2e38591f515a |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.