Triple
T28874666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLDM |
E732232
|
entity |
| Predicate | specialUnitRole |
P9463
|
FINISHED |
| Object | naval special 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: naval special operations | Statement: [TLDM, specialUnitRole, naval special operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialUnitRole Context triple: [TLDM, specialUnitRole, naval special operations]
-
A.
unitSpecialization
Indicates that one unit is a specialized or more specific version of another unit within a hierarchical or categorical relationship.
-
B.
specialRole
Indicates that an entity holds a distinctive or exceptional function, status, or responsibility in relation to another entity or context.
-
C.
specialForcesInvolved
Indicates that special forces units participate in or are involved in the referenced action, event, or operation.
-
D.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
E.
hasSpecialUnit
Indicates that an entity possesses or is associated with a distinct, designated unit that has a special role, function, or status.
- 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_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 7:36 a.m.