Triple
T28390965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Query Syntax |
E719153
|
entity |
| Predicate | supportsComparisonOperator |
P185583
|
FINISHED |
| Object | > |
—
|
NE NERFINISHED |
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: > | Statement: [Advanced Query Syntax, supportsComparisonOperator, >]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsComparisonOperator Context triple: [Advanced Query Syntax, supportsComparisonOperator, >]
-
A.
enablesComparison
chosen
Indicates that one entity provides the means or conditions necessary to compare two or more entities with each other.
-
B.
hasComparison
Indicates that one entity is being evaluated or contrasted relative to another entity based on some shared attribute or criterion.
-
C.
hasComparisonCriterion
Indicates that one entity is used as the basis or standard by which another entity is compared or evaluated.
-
D.
supportsIntegerOperations
Indicates that the subject is capable of performing or handling operations involving integer values.
-
E.
supportsBooleanOperators
Indicates that the subject allows the use of Boolean operators (such as AND, OR, NOT) within its operations or expressions.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a009273634c8190b5b9c87053b56760 |
completed | May 10, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_6a0092171230819096e4274dd97e0410 |
completed | May 10, 2026, 2:11 p.m. |
Created at: April 28, 2026, 1:13 a.m.