Triple
T34199790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro Virtute Decoration |
E877344
|
entity |
| Predicate | claspAvailable |
P178519
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pro Virtute Decoration, claspAvailable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claspAvailable Context triple: [Pro Virtute Decoration, claspAvailable, yes]
-
A.
claspIndicates
Indicates a relationship where one entity grasps, holds, or fastens onto another, typically in a secure or enclosing manner.
-
B.
claspSystem
Indicates that one entity is part of, or operates within, a clasp-based mechanism or fastening system associated with another entity.
-
C.
claspForAdditionalService
Indicates that one entity serves as a clasp or fastening component intended to support or enable an additional service or function for another entity.
-
D.
claspPolicy
Indicates that an entity enforces or is governed by a specific CLASP (or similar) security or access control policy.
-
E.
hasClasps
Indicates that one entity is equipped with or features clasps that fasten, secure, or attach it to another entity or its parts.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:55 a.m.