Triple
T34543612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CartoCSS |
E886865
|
entity |
| Predicate | supportsLabelPlacementOptions |
P162301
|
FINISHED |
| Object | text placement |
—
|
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: text placement | Statement: [CartoCSS, supportsLabelPlacementOptions, text placement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLabelPlacementOptions Context triple: [CartoCSS, supportsLabelPlacementOptions, text placement]
-
A.
colorPlacement
Indicates the spatial or contextual position where a particular color is applied or appears in relation to an entity.
-
B.
mapLabelPosition
chosen
Indicates the spatial or relative placement of a label on or around a map or mapped feature.
-
C.
supportsPosition
Indicates that one entity endorses, upholds, or provides backing for the stance, viewpoint, or role represented by another entity.
-
D.
labelLocation
Indicates that a label or identifier is associated with a specific spatial or geographic location.
-
E.
hasNumberPlacement
Indicates that a specific number is assigned to or occupies a particular position or location relative to something else.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:02 a.m.