Triple
T1967999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safety Management Certificate |
E42732
|
entity |
| Predicate | hasValidityPeriod |
P33304
|
FINISHED |
| Object | maximum 5 years |
—
|
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: maximum 5 years | Statement: [Safety Management Certificate, hasValidityPeriod, maximum 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasValidityPeriod Context triple: [Safety Management Certificate, hasValidityPeriod, maximum 5 years]
-
A.
hasValidity
Indicates that something possesses a period or condition during which it is considered legally, logically, or functionally acceptable or in force.
-
B.
hasValidityPeriodAnonymousCard
Indicates that an anonymous card is associated with a specific time period during which it is valid or usable.
-
C.
hasValidityPeriodPersonalCard
Indicates that a personal card is associated with a specific time period during which it is valid or in effect.
-
D.
validityPeriodForAdults
Indicates the time span during which something is considered valid or applicable specifically for adults.
-
E.
validityPeriodForMinors
Indicates the time span during which something is considered valid specifically for minors.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3cf15048190a51f73ed85e1b958 |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb16a6db48190af04012e8ed2269f |
completed | March 7, 2026, 5:02 a.m. |
Created at: March 4, 2026, 7:36 p.m.