Triple
T8121124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Force Z |
E189609
|
entity |
| Predicate | locationOfMajorEngagement |
P37770
|
FINISHED |
| Object | off Kuantan, Malaya |
—
|
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: off Kuantan, Malaya | Statement: [Force Z, locationOfMajorEngagement, off Kuantan, Malaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfMajorEngagement Context triple: [Force Z, locationOfMajorEngagement, off Kuantan, Malaya]
-
A.
placeOfMainEngagement
Indicates the primary location where an entity carries out its main activities, operations, or engagements.
-
B.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
-
C.
battleOccurredNear
chosen
Indicates that a battle took place in spatial proximity to a specified location or entity.
-
D.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
E.
battleBelligerentAtSite
Indicates that a particular belligerent (participant in a battle) was present and engaged in that battle at a specified site or location.
- 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_69ca82bb74848190afb1f18640632c10 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
Created at: March 30, 2026, 5:33 p.m.