Triple
T17561088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoServer |
E427695
|
entity |
| Predicate | supportsReprojection |
P100900
|
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: [GeoServer, supportsReprojection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReprojection Context triple: [GeoServer, supportsReprojection, yes]
-
A.
hasProjectionSystem
Indicates that one entity uses or is defined by a particular coordinate or map projection system associated with another entity.
-
B.
projectionRequirement
Indicates a requirement that one entity be projected, mapped, or represented onto another according to specified criteria or constraints.
-
C.
supports3DTransforms
Indicates that one entity provides or is compatible with three-dimensional transform capabilities for another entity or within a given context.
-
D.
isSupportedFor
chosen
Indicates that one entity provides compatibility, assistance, or backing necessary for another entity’s proper use or operation.
-
E.
supportsRasterization
Indicates that one entity provides the capability or functionality for another entity to perform rasterization operations.
- 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_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.