Triple
T116823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASME Boiler and Pressure Vessel Code |
E2355
|
entity |
| Predicate | updateFrequency |
P85
|
FINISHED |
| Object | periodically revised |
—
|
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 revised | Statement: [ASME Boiler and Pressure Vessel Code, updateFrequency, periodically revised]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updateFrequency Context triple: [ASME Boiler and Pressure Vessel Code, updateFrequency, periodically revised]
-
A.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
B.
meetingFrequency
Indicates how often a meeting or recurring gathering takes place over a given period.
-
C.
frequency
chosen
Indicates how often an event, action, or relationship occurs within a given period or context.
-
D.
awardedFrequency
Indicates how often an award or recognition is given within a specified time period.
-
E.
publicationFrequency
Indicates how often a publication or content is issued, released, or made available over a given period.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a256456d908190b52c937fe6c4343f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.