Triple
T30951706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 118th Wing |
E788562
|
entity |
| Predicate | activationContext |
P121032
|
FINISHED |
| Object | Title 32 of the United States Code |
—
|
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: Title 32 of the United States Code | Statement: [118th Wing, activationContext, Title 32 of the United States Code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activationContext Context triple: [118th Wing, activationContext, Title 32 of the United States Code]
-
A.
activityContext
chosen
Indicates the situational setting or circumstances in which an activity occurs, such as its purpose, environment, or relevant conditions.
-
B.
activationProperty
Indicates a relationship where one entity specifies the conditions, parameters, or characteristics that determine how another entity becomes active or is triggered.
-
C.
activationType
Indicates the specific manner or mechanism by which an activation or triggering event occurs between entities.
-
D.
activationLocation
Indicates the place or site where an activation event or process occurs.
-
E.
activationBy
Indicates that one entity initiates, triggers, or enhances the activity, function, or state of 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 8:53 p.m.