Triple
T2883507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MARSOC Raiders |
E59450
|
entity |
| Predicate | primaryOperatorRank |
P42566
|
FINISHED |
| Object | enlisted Marines |
—
|
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: enlisted Marines | Statement: [MARSOC Raiders, primaryOperatorRank, enlisted Marines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOperatorRank Context triple: [MARSOC Raiders, primaryOperatorRank, enlisted Marines]
-
A.
primaryOperator
Indicates that an entity serves as the main or leading operator responsible for performing or overseeing a specified operation or process in relation to another entity.
-
B.
primaryHighSpeedOperator
Indicates that an entity serves as the main operator responsible for providing high-speed service or functionality to another entity.
-
C.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
D.
largestOperator
Indicates that the subject is the operator with the greatest size, capacity, or scale among a specified set of operators.
-
E.
typicalOperatorType
Indicates the usual or most common type or category of operator associated with a given entity or context.
- F. None of above. chosen
Provenance (4 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe02c238881908f7a349563c388bf |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:03 p.m.