Triple
T17561272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ST_Buffer |
E427699
|
entity |
| Predicate | supportsGeometryTypes |
P24486
|
FINISHED |
| Object | points |
—
|
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: points | Statement: [ST_Buffer, supportsGeometryTypes, points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGeometryTypes Context triple: [ST_Buffer, supportsGeometryTypes, points]
-
A.
hasGeometry
Indicates that an entity is associated with a specific geometric representation or spatial form.
-
B.
supportsSpatialQueries
Indicates that the subject system or component is capable of performing spatial (location- or geometry-based) queries on data.
-
C.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
testGeometry
Indicates that an entity is involved in evaluating, validating, or analyzing geometric properties, shapes, or spatial relationships.
-
E.
includesFeatureTypes
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456267e208190a1238fbe1a535bb0 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.