Triple
T28390960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Query Syntax |
E719153
|
entity |
| Predicate | supportsSyntaxElement |
P202555
|
FINISHED |
| Object | property:value pairs |
—
|
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: property:value pairs | Statement: [Advanced Query Syntax, supportsSyntaxElement, property:value pairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSyntaxElement Context triple: [Advanced Query Syntax, supportsSyntaxElement, property:value pairs]
-
A.
definesSyntaxElement
Indicates that one entity specifies or establishes the syntactic form or structure of another entity.
-
B.
explainsSyntaxElement
Indicates that one entity provides an explanation or clarification of the syntax or structural role of another element.
-
C.
supportsExpressionType
Indicates that one entity is capable of handling, processing, or being compatible with a specified type of expression.
-
D.
supportsPlaceholderSyntax
Indicates that one entity provides or is compatible with a placeholder-based syntax used for parameterization or substitution in another entity.
-
E.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_6a0091ac9ff08190b635eac6aa3f6128 |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 28, 2026, 1:13 a.m.