Triple
T6519585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRU |
E148346
|
entity |
| Predicate | hasSpecificationType |
P45345
|
FINISHED |
| Object | open standard |
—
|
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: open standard | Statement: [SRU, hasSpecificationType, open standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecificationType Context triple: [SRU, hasSpecificationType, open standard]
-
A.
hasSpecification
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasSpecificationSection
Indicates that an entity includes or is associated with a particular section dedicated to specifications.
-
D.
specType
chosen
Indicates the specific type or category of a specification that an entity is associated with.
-
E.
hasStandardType
Indicates that something conforms to or is categorized under a defined standard classification or type.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac11d0e481908103c4b51de9521e |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.