Triple
T2807127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24th Marine Expeditionary Unit |
E54078
|
entity |
| Predicate | deploymentPattern |
P4119
|
FINISHED |
| Object | rotational deployments |
—
|
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: rotational deployments | Statement: [24th Marine Expeditionary Unit, deploymentPattern, rotational deployments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentPattern Context triple: [24th Marine Expeditionary Unit, deploymentPattern, rotational deployments]
-
A.
distributionPattern
Indicates the characteristic way in which something is spread, arranged, or allocated across a space, group, or set.
-
B.
deploymentModel
Indicates the type or manner in which a system, service, or resource is deployed or made available (e.g., on-premises, cloud, hybrid).
-
C.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
-
D.
distributedAs
Indicates that something is allocated, delivered, or spread out according to a particular pattern, rule, or distribution scheme.
-
E.
typicalDeployment
chosen
Indicates that one entity represents the standard or most commonly used deployment configuration or pattern for the other 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.