Triple
T17561090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoServer |
E427695
|
entity |
| Predicate | supportsTransactionalEditing |
P29730
|
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, supportsTransactionalEditing, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTransactionalEditing Context triple: [GeoServer, supportsTransactionalEditing, yes]
-
A.
supportsConcurrentEditing
Indicates that multiple users can edit the same item or resource at the same time without blocking one another.
-
B.
supportsTransactions
chosen
Indicates that one entity provides the capability for another entity to perform or manage transactions reliably.
-
C.
supportsEditingType
Indicates that one entity enables or allows another entity to perform or handle a specified type of editing.
-
D.
hasEditingFeature
Indicates that an entity possesses a capability or function related to modifying or editing content.
-
E.
supportsSceneEditing
Indicates that an entity provides the capability to modify, arrange, or otherwise edit a scene within a given environment or application.
- 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.