Triple
T10330052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WFS |
E242850
|
entity |
| Predicate | supportsCoordinateReferenceSystems |
P40909
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [WFS, supportsCoordinateReferenceSystems, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCoordinateReferenceSystems Context triple: [WFS, supportsCoordinateReferenceSystems, true]
-
A.
hasSummitCoordinateSystem
Indicates that a summit or peak is associated with a specific coordinate system used to define its geographic position.
-
B.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
C.
supportsReferenceModes
chosen
Indicates that an entity provides or is compatible with specific reference modes for identifying or accessing other entities.
-
D.
usesEllipsoid
Indicates that one entity employs or is based on a particular ellipsoid as its geometric or reference model.
-
E.
hasCoordinates
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7fb77348190ac8ff887f6f03450 |
completed | April 7, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f760e88190abea6dcc4f04f2c1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.