Triple
T23228442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerigo |
E581077
|
entity |
| Predicate | usedInCartographyBy |
P136577
|
FINISHED |
| Object | Venetian cartographers |
—
|
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: Venetian cartographers | Statement: [Cerigo, usedInCartographyBy, Venetian cartographers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCartographyBy Context triple: [Cerigo, usedInCartographyBy, Venetian cartographers]
-
A.
cartographicUse
chosen
Indicates the way in which something is used or intended to be used within a cartographic or map-making context.
-
B.
cartographyBy
Indicates that one entity is the creator or producer of the cartographic work (such as a map or chart) associated with another entity.
-
C.
cartographicSignificance
Indicates the importance or relevance of something within the context of mapping or geographic representation.
-
D.
cartographicWork
Indicates a relationship where one entity is a cartographic work (such as a map or chart) that represents geographic information about another entity.
-
E.
cartographicInnovation
Indicates the introduction or use of new methods, techniques, or technologies in map-making or geographic representation.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192302e508190b286c284a261f172 |
completed | April 29, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.