Triple
T6079705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burano |
E135490
|
entity |
| Predicate | colorRegulation |
P62473
|
FINISHED |
| Object | house colors regulated by local authorities |
—
|
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: house colors regulated by local authorities | Statement: [Burano, colorRegulation, house colors regulated by local authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorRegulation Context triple: [Burano, colorRegulation, house colors regulated by local authorities]
-
A.
colors
Indicates that one entity assigns, describes, or provides the color or colors of another entity.
-
B.
capeColor
Indicates the color attribute associated with a cape worn or possessed by an entity.
-
C.
colorTheory
Indicates a relationship where principles or concepts about how colors interact, combine, or affect perception are applied or referenced between entities.
-
D.
colorSystem
chosen
Indicates that one entity is a system or scheme used to define, organize, or represent the colors of another entity.
-
E.
colorCharge
Indicates a relationship where an entity possesses a specific quantum color charge (such as red, green, or blue) in the context of strong nuclear interactions.
- 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_69c0087ad31c8190ab936e0ff28614b6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0577209b88190afe5b1365cf6436d |
completed | March 22, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:11 p.m.