Triple
T4616900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO standards |
E100888
|
entity |
| Predicate | areReviewedEvery |
P56962
|
FINISHED |
| Object | 5 years (typical review cycle) |
—
|
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: 5 years (typical review cycle) | Statement: [ISO standards, areReviewedEvery, 5 years (typical review cycle)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areReviewedEvery Context triple: [ISO standards, areReviewedEvery, 5 years (typical review cycle)]
-
A.
reviewedBy
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
B.
canReview
Indicates that one entity has the permission or ability to evaluate, assess, or provide feedback on another entity.
-
C.
checkedBy
Indicates that an entity has been examined, verified, or reviewed by another entity.
-
D.
reassessedAfter
Indicates that one entity is evaluated or reviewed again at a time point that occurs after another specified event or assessment.
-
E.
requiresAssessmentOf
Indicates that one entity necessitates an evaluation, review, or judgment to be performed on another entity before proceeding or fulfilling a condition.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:12 p.m.