Triple
T32515951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST P-256 family |
E831061
|
entity |
| Predicate | approxIntroductionPeriod |
P60853
|
FINISHED |
| Object | late 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: late 1990s | Statement: [NIST P-256 family, approxIntroductionPeriod, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxIntroductionPeriod Context triple: [NIST P-256 family, approxIntroductionPeriod, late 1990s]
-
A.
approximateIntroductionPeriod
chosen
Indicates the approximate time period during which an entity was first introduced or came into use.
-
B.
timePeriodApproximation
Indicates that the associated time period is an estimate or approximation rather than an exact, precise value.
-
C.
activePeriodApproximate
Indicates that the time span during which an entity was active is known only approximately rather than as precise dates.
-
D.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
E.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 1, 2026, 1 a.m.