Triple
T20817348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEGIS combat system |
E512476
|
entity |
| Predicate | firstOperationalDeployment |
P3273
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [AEGIS combat system, firstOperationalDeployment, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOperationalDeployment Context triple: [AEGIS combat system, firstOperationalDeployment, 1983]
-
A.
firstOperationalUse
Indicates the point in time or context when something is used operationally for the very first time.
-
B.
firstDeployedIn
Indicates the time or place where something (such as a system, product, or technology) was initially put into operational use or service.
-
C.
firstDeployed
chosen
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
-
D.
firstOfficialUse
Indicates the earliest point in time when something was formally or officially put into use.
-
E.
firstOperationalCargoMissionDate
Indicates the calendar date on which an entity conducted its first operational mission carrying cargo.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2f429388190809dd532278fe310 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.