Triple
T3895056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 41 (Independent) Commando Royal Marines |
E88148
|
entity |
| Predicate | sharesLineageWith |
P18399
|
FINISHED |
| Object | other numbered Royal Marines Commandos |
—
|
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: other numbered Royal Marines Commandos | Statement: [41 (Independent) Commando Royal Marines, sharesLineageWith, other numbered Royal Marines Commandos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLineageWith Context triple: [41 (Independent) Commando Royal Marines, sharesLineageWith, other numbered Royal Marines Commandos]
-
A.
sharesTrunkLineWith
Indicates that two entities are connected to or use the same primary communication or utility trunk line.
-
B.
sharesOwnershipWith
Indicates that two or more entities jointly hold ownership rights or stakes in the same asset, resource, or organization.
-
C.
sharesHistoryWith
Indicates that two entities have a common or overlapping past, such as shared experiences, events, or origins.
-
D.
sharesNameRootWith
Indicates that two entities have names derived from the same linguistic root or base form.
-
E.
sharesCommonAncestorWith
chosen
Indicates that two entities have at least one ancestor in common in their lineage or hierarchy.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.