Triple
T38477012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IX |
E915574
|
entity |
| Predicate | mapNameStyle |
P190939
|
FINISHED |
| Object | Roman numeral |
—
|
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: Roman numeral | Statement: [IX, mapNameStyle, Roman numeral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapNameStyle Context triple: [IX, mapNameStyle, Roman numeral]
-
A.
mapLabel
Indicates that a label or name is assigned to a map or mapped entity for identification or display.
-
B.
mapTheme
Indicates a thematic relationship where a map is associated with, organized by, or visually represents a particular theme or subject.
-
C.
mapConvention
Indicates a relationship where one representation or system is translated or aligned to another according to a defined set of mapping rules or conventions.
-
D.
mapSymbolStandard
Indicates that a map symbol conforms to, or is defined according to, a particular cartographic standard or specification.
-
E.
mapColor
Indicates a relationship where a map region or area is assigned or associated with a specific color, typically for visualization or categorization purposes.
- F. None of above. chosen
Provenance (4 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd34596288190b8e34a7a20b4c0db |
completed | May 7, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd31227708190a7df213597e66ca8 |
completed | May 7, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:31 p.m.