Triple
T1492192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPARQL 1.1 |
E29603
|
entity |
| Predicate | addsFeature |
P203
|
FINISHED |
| Object | update operations |
—
|
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: update operations | Statement: [SPARQL 1.1, addsFeature, update operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsFeature Context triple: [SPARQL 1.1, addsFeature, update operations]
-
A.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
featuresAction
Indicates that one entity includes, presents, or showcases a particular action as a notable characteristic or component.
-
C.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
D.
postAmendmentFeature
Indicates that a feature, characteristic, or condition applies only after an amendment has been made or has taken effect.
-
E.
passesFeature
Indicates that one entity successfully satisfies, verifies, or meets the criteria of a specified feature or test condition associated with another entity.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c4f0c88190a97ba4910c1a5d85 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c48902808190a8028d359bcf123e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.