Triple
T17560967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeoJSON |
E427694
|
entity |
| Predicate | isMachineReadable |
P5372
|
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: [GeoJSON, isMachineReadable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMachineReadable Context triple: [GeoJSON, isMachineReadable, true]
-
A.
machineReadable
chosen
Indicates that something is in a format that can be automatically processed or interpreted by a computer without human intervention.
-
B.
usedInMachineReadableContexts
Indicates that something is employed or applied within formats or environments that can be automatically processed and interpreted by machines.
-
C.
typicalRecognitionFormat
Indicates the usual or standard format in which something is recognized, identified, or acknowledged.
-
D.
canBeReadWith
Indicates that one entity is suitable or compatible to be read or interpreted together with another entity.
-
E.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
- 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.