Triple
T4364916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Special Operations Command |
E98747
|
entity |
| Predicate | dateActivated |
P7730
|
FINISHED |
| Object | 22 May 1990 |
—
|
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: 22 May 1990 | Statement: [Air Force Special Operations Command, dateActivated, 22 May 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateActivated Context triple: [Air Force Special Operations Command, dateActivated, 22 May 1990]
-
A.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
B.
activeFrom
chosen
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
C.
automationDate
Indicates the date on which an action, process, or system becomes automated or is scheduled to be handled automatically.
-
D.
dateGranted
Indicates the specific date on which a right, status, or permission was formally conferred or approved.
-
E.
inscriptionDate
Indicates the date on which an inscription was created, carved, or formally recorded.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351fea3e88190807b99868982c491 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.