Triple
T20795794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uniform Physical Condition Standards |
E511905
|
entity |
| Predicate | implementationPeriod |
P141565
|
FINISHED |
| Object | late 1990s onward |
—
|
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 onward | Statement: [Uniform Physical Condition Standards, implementationPeriod, late 1990s onward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementationPeriod Context triple: [Uniform Physical Condition Standards, implementationPeriod, late 1990s onward]
-
A.
administrationPeriod
Indicates the time span during which an entity is responsible for administering, managing, or governing another entity or resource.
-
B.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
C.
upgradePeriod
Indicates the time span or interval during which an upgrade is valid, active, or can be performed.
-
D.
agingPeriod
Indicates the length of time something is allowed or intended to mature or age before reaching its final or usable state.
-
E.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
- F. None of above. chosen
Provenance (4 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2acbac48190b9b46c8c2a761bd8 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:39 p.m.