Triple
T21989701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Industrial Standards |
E543049
|
entity |
| Predicate | revisionPolicy |
P146193
|
FINISHED |
| Object | periodically reviewed |
—
|
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: periodically reviewed | Statement: [Japanese Industrial Standards, revisionPolicy, periodically reviewed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisionPolicy Context triple: [Japanese Industrial Standards, revisionPolicy, periodically reviewed]
-
A.
editingPolicy
Indicates that one entity defines or enforces the rules, constraints, or procedures governing how another entity may be edited or modified.
-
B.
referencePolicy
Indicates that one entity defines rules or guidelines governing how another entity may be referred to, cited, or mentioned.
-
C.
preservationPolicy
Indicates the rules or strategy governing how something is maintained, protected, and retained over time.
-
D.
gradingPolicy
Indicates the rules or criteria that determine how performance or work is evaluated and assigned grades.
-
E.
archivePolicy
Indicates the rules or conditions governing how items are stored, retained, and managed in an archive.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270cb67c81909a3aa2dc61c1894f |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:05 p.m.