Triple
T20795776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uniform Physical Condition Standards |
E511905
|
entity |
| Predicate | inspectionScope |
P51335
|
FINISHED |
| Object | site |
—
|
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: site | Statement: [Uniform Physical Condition Standards, inspectionScope, site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspectionScope Context triple: [Uniform Physical Condition Standards, inspectionScope, site]
-
A.
isInspected
Indicates that an entity is examined or checked by another entity to assess its condition, quality, or compliance.
-
B.
inspectionRequired
Indicates that an entity must undergo an inspection before it can proceed, be used, or be approved.
-
C.
reviewScope
chosen
Indicates the extent, boundaries, or aspects of something that are covered, considered, or evaluated during a review.
-
D.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
E.
investigativeScope
Indicates the range or extent of subjects, issues, or activities that an investigation is intended to examine or cover.
- 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2acbac48190b9b46c8c2a761bd8 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:39 p.m.