Triple
T36775702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cadore |
E908611
|
entity |
| Predicate | notablePersonFromRegion |
P39809
|
FINISHED |
| Object | Titian |
E51518
|
NE 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: Titian | Statement: [Cadore, notablePersonFromRegion, Titian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePersonFromRegion Context triple: [Cadore, notablePersonFromRegion, Titian]
-
A.
notableArtistFromRegion
Indicates that an artist is recognized as notable and originates from, or is strongly associated with, a particular geographic region.
-
B.
notableIndividuals
Indicates that certain individuals are recognized as particularly important, famous, or influential in relation to something.
-
C.
notableCulturalFigure
Indicates that a person holds significant influence or recognition within a culture’s arts, traditions, values, or public life.
-
D.
notableInRegion
chosen
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
E.
notablePublicFigure
Indicates that the subject is widely recognized and holds a significant public profile or influence in society.
- F. None of above.
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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d179bd4cc81908a0039e4b3bfbe25 |
completed | June 25, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.