Triple
T313949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Readiness Brigades |
E7665
|
entity |
| Predicate | logisticsSupport |
P5899
|
FINISHED |
| Object | organic brigade-level logistics |
—
|
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: organic brigade-level logistics | Statement: [Readiness Brigades, logisticsSupport, organic brigade-level logistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logisticsSupport Context triple: [Readiness Brigades, logisticsSupport, organic brigade-level logistics]
-
A.
mainCargo
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
B.
assistedShip
Indicates that one entity helped or supported a ship in performing an operation, task, or journey.
-
C.
airSupport
Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
-
D.
supplyChain
chosen
Indicates a relationship where one entity participates in providing, transferring, or managing goods, services, or information to another as part of a sequential production and distribution process.
-
E.
carriedBy
Indicates that one entity is physically supported and transported by 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ea4bd6a081909bdb57602c7093b4 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e9428098819089d5950cd2c96dc4 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.