Triple
T2148176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 528th Sustainment Brigade (Special Operations) (Airborne) |
E47115
|
entity |
| Predicate | operationsArea |
P82
|
FINISHED |
| Object | worldwide |
—
|
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: worldwide | Statement: [528th Sustainment Brigade (Special Operations) (Airborne), operationsArea, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationsArea Context triple: [528th Sustainment Brigade (Special Operations) (Airborne), operationsArea, worldwide]
-
A.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
-
B.
areaServed
chosen
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
C.
collaborationArea
Indicates the domain, topic, or field in which two or more entities work together or collaborate.
-
D.
areaComponent
Indicates that one area is a constituent or sub-area that forms part of a larger area.
-
E.
operatesWithin
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined 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_69a88a1933e0819094f18426ed74180f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbeaa14bc81908486683decd7ae42 |
completed | March 7, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_69abbd9846e88190b6c2941dd9ce7749 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.