Triple
T16946747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 19111 |
E411085
|
entity |
| Predicate | definesMetadata |
P44503
|
FINISHED |
| Object | Identifiers for coordinate reference system components |
—
|
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: Identifiers for coordinate reference system components | Statement: [ISO 19111, definesMetadata, Identifiers for coordinate reference system components]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMetadata Context triple: [ISO 19111, definesMetadata, Identifiers for coordinate reference system components]
-
A.
dynamicMetadataSupport
Indicates that the subject system or component is capable of handling metadata that can change or be updated at runtime rather than being fixed or static.
-
B.
definesType
Indicates that one entity specifies or establishes the type or classification of another entity.
-
C.
definesEntity
Indicates that one entity specifies, determines, or establishes the identity, nature, or boundaries of another entity.
-
D.
metadataType
chosen
Indicates that one entity specifies the kind or category of metadata associated with another entity.
-
E.
definesService
Indicates that one entity specifies or establishes the service provided or implemented by another entity.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb25e0c8190948e62d9575ae9cd |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.