Triple
T237817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASME B31 Pressure Piping Code |
E4859
|
entity |
| Predicate | updateCycle |
P7825
|
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 B31 Pressure Piping Code, updateCycle, periodically revised]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updateCycle Context triple: [ASME B31 Pressure Piping Code, updateCycle, periodically revised]
-
A.
updateProcess
Indicates the action or procedure by which an existing item, system, or state is modified to a newer or revised version.
-
B.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
C.
readingsCycle
chosen
Indicates that there is a recurring or cyclical pattern in the readings associated with an entity or process.
-
D.
followsCycle
Indicates that one entity adheres to or repeats a recurring sequence, pattern, or cycle defined or exemplified by another entity.
-
E.
upgradePhase
Indicates the stage or step within a process where an entity is being upgraded or transitioned to a more advanced version or state.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25dacf60c8190a5c3ef455b9a8b20 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b5f27208190ae13f34037fe582b |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.