Triple
T33437433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLD |
E856267
|
entity |
| Predicate | symbolizerType |
P13707
|
FINISHED |
| Object | PointSymbolizer |
—
|
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: PointSymbolizer | Statement: [SLD, symbolizerType, PointSymbolizer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolizerType Context triple: [SLD, symbolizerType, PointSymbolizer]
-
A.
pointsSymbolize
Indicates that specific points are used to represent or stand for particular meanings, concepts, or values.
-
B.
mapSymbolStandard
Indicates that a map symbol conforms to, or is defined according to, a particular cartographic standard or specification.
-
C.
symbolType
chosen
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
-
D.
symbolicStyle
Indicates that one entity employs or is characterized by a particular symbolic or emblematic style defined by the other entity.
-
E.
lineSymbol
Indicates that one entity is used as a line-style or line-representation symbol for 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:36 a.m.