Triple
T22761319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 40 Commando |
E562996
|
entity |
| Predicate | roleWithinRoyalMarines |
P9463
|
FINISHED |
| Object | commando unit within 3 Commando Brigade |
—
|
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: commando unit within 3 Commando Brigade | Statement: [40 Commando, roleWithinRoyalMarines, commando unit within 3 Commando Brigade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleWithinRoyalMarines Context triple: [40 Commando, roleWithinRoyalMarines, commando unit within 3 Commando Brigade]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
joinedRoyalNavy
Indicates that an individual entered into service as a member of the Royal Navy.
-
C.
statusWithRoyalNavy
Indicates the formal standing, role, or condition an entity has in relation to the Royal Navy (e.g., active service, retired, affiliated, or none).
-
D.
enteredRoyalNavyFrontlineService
Indicates that an entity began active duty or operational deployment in the frontline forces of the Royal Navy.
-
E.
militaryRankScope
Indicates the hierarchical level or range of authority that a military rank applies to within an organizational or operational context.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a7c45b881908b29ba1439038789 |
completed | April 29, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:26 p.m.