Triple
T25843318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FPDA Integrated Area Defence System Headquarters |
E650995
|
entity |
| Predicate | supportsDefenceOf |
P129572
|
FINISHED |
| Object | Malaysia |
—
|
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: Malaysia | Statement: [FPDA Integrated Area Defence System Headquarters, supportsDefenceOf, Malaysia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDefenceOf Context triple: [FPDA Integrated Area Defence System Headquarters, supportsDefenceOf, Malaysia]
-
A.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
B.
providesDefence
chosen
Indicates that one entity offers protection or defensive support to another entity.
-
C.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
D.
alsoDefendedIn
Indicates that the same entity or case was defended in an additional context, such as another court, proceeding, or jurisdiction.
-
E.
supportsProsecutionIn
Indicates that an entity provides assistance or backing to the prosecution side within a specified legal case or jurisdiction.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 22, 2026, 7:50 a.m.