Triple
T28874665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLDM |
E732232
|
entity |
| Predicate | specialUnitFullName |
P126453
|
FINISHED |
| Object | Pasukan Khas Laut |
—
|
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: Pasukan Khas Laut | Statement: [TLDM, specialUnitFullName, Pasukan Khas Laut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialUnitFullName Context triple: [TLDM, specialUnitFullName, Pasukan Khas Laut]
-
A.
militaryUnitName
Indicates the specific official name assigned to a military unit in the context of a broader relationship or record.
-
B.
isNamedMilitaryUnit
chosen
Indicates that the subject is a military unit that has been given a specific official name.
-
C.
hasSpecialUnit
Indicates that an entity possesses or is associated with a distinct, designated unit that has a special role, function, or status.
-
D.
unitSpecialization
Indicates that one unit is a specialized or more specific version of another unit within a hierarchical or categorical relationship.
-
E.
notableTeamUnit
Indicates that an entity is a significant or distinguished member unit (such as a player or component) of a particular team.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 7:36 a.m.