Triple
T11948932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRSG |
E284376
|
entity |
| Predicate | typeOfSupportUnit |
P55850
|
FINISHED |
| Object | combat service 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: combat service support | Statement: [MRSG, typeOfSupportUnit, combat service support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSupportUnit Context triple: [MRSG, typeOfSupportUnit, combat service support]
-
A.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
B.
supportUnits
Indicates that one entity provides assistance, resources, or reinforcement to another entity, often in an operational or functional context.
-
C.
typicalSupportedUnitType
chosen
Indicates the kind or category of unit that an entity is normally designed or expected to support.
-
D.
supportedUnit
Indicates that one entity provides assistance, resources, or backing to another entity functioning as a unit or sub-organization.
-
E.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90346825c8190ab4482a1fc8eed56 |
completed | April 10, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.