Triple
T28400384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OC-3 |
E719379
|
entity |
| Predicate | commonDeploymentEra |
P178347
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [OC-3, commonDeploymentEra, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonDeploymentEra Context triple: [OC-3, commonDeploymentEra, 1990s]
-
A.
eraOfDeployment
chosen
Indicates the time period or historical era during which something was put into use or made operational.
-
B.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
C.
commandEra
Indicates the time period or era during which an entity held command or exercised authoritative control.
-
D.
associatedProductionEra
Indicates a relationship where something is linked to the specific time period or era during which it was produced or created.
-
E.
managedEra
Indicates that one entity oversaw, directed, or was responsible for the management of a particular historical or temporal period associated with 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 28, 2026, 1:19 a.m.