Triple
T17561089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoServer |
E427695
|
entity |
| Predicate | supportsTransactionalWFS |
P127963
|
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, supportsTransactionalWFS, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTransactionalWFS Context triple: [GeoServer, supportsTransactionalWFS, yes]
-
A.
supportsTransactions
Indicates that one entity provides the capability for another entity to perform or manage transactions reliably.
-
B.
supportsTransactionIsolationLevel
Indicates that an entity (such as a system, component, or resource) is capable of operating with or honoring a specified transaction isolation level.
-
C.
supportsOperationsWith
Indicates that one entity enables, facilitates, or is compatible with the execution of operations involving another entity.
-
D.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
E.
supportsSpatialQueries
Indicates that the subject system or component is capable of performing spatial (location- or geometry-based) queries on data.
- 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_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. |
| PDg | Predicate description generation | batch_69e3bbb50b448190a59dd4be33c76db7 |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:50 a.m.