Triple
T33437379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetCapabilities |
E856266
|
entity |
| Predicate | supportsDiscoveryOf |
P98632
|
FINISHED |
| Object | map layers |
—
|
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: map layers | Statement: [GetCapabilities, supportsDiscoveryOf, map layers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDiscoveryOf Context triple: [GetCapabilities, supportsDiscoveryOf, map layers]
-
A.
supportedDiscoveryOf
Indicates that one entity aided, enabled, or contributed to another entity’s act of discovering something.
-
B.
supportsFinding
Indicates that one entity provides the capability or functionality needed to perform, enable, or carry out a particular finding operation on another entity or resource.
-
C.
hasDiscoveryFeature
chosen
Indicates that an entity includes or supports a capability for discovering, finding, or surfacing other relevant entities, items, or information.
-
D.
namedForDiscoveryOf
Indicates that one entity is named in recognition of another entity’s discovery of something.
-
E.
sharedDiscoveryWith
Indicates that two or more entities jointly participated in, contributed to, or are mutually associated with the same discovery.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:36 a.m.