Triple
T18379362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 459th Operations Group |
E446401
|
entity |
| Predicate | activeComponent |
P130906
|
FINISHED |
| Object | Reserve |
—
|
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: Reserve | Statement: [459th Operations Group, activeComponent, Reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeComponent Context triple: [459th Operations Group, activeComponent, Reserve]
-
A.
activeAs
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
-
B.
componentAct
Indicates that an action or behavior is performed by a component as part of a larger system or process.
-
C.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
D.
activeInEvent
Indicates that an entity participates in or is involved in carrying out actions within a particular event.
-
E.
activatedAs
Indicates that one entity has been put into an active or operational state in the role or capacity of another specified entity.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51799e0f4819089e8af04888549bf |
completed | April 19, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:45 a.m.