Triple
T3358376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cannon Cockers |
E70657
|
entity |
| Predicate | hasServiceBranchRole |
P11687
|
FINISHED |
| Object | ground combat support |
—
|
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: ground combat support | Statement: [The Cannon Cockers, hasServiceBranchRole, ground combat support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceBranchRole Context triple: [The Cannon Cockers, hasServiceBranchRole, ground combat support]
-
A.
hasServicePatternRole
Indicates that an entity participates in a service pattern with a specific functional role or responsibility within that pattern.
-
B.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
C.
hasSubService
Indicates that one service includes or is composed of another, more specific service as a subordinate or component part.
-
D.
hasSubsidiaryRoleInGroup
Indicates that an entity holds a secondary or supporting role within a specified group.
-
E.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb26523cc819091006fde7beb32e4 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.