Triple
T32800709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cine Odeon |
E838887
|
entity |
| Predicate | iconic |
P37670
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cine Odeon, iconic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iconic Context triple: [Cine Odeon, iconic, true]
-
A.
iconicTrait
Indicates that a trait is emblematic or strongly characteristic of an entity, making it widely recognized as a defining feature of that entity.
-
B.
iconicFeature
chosen
Indicates that something serves as a distinctive, widely recognized characteristic or symbol of another entity.
-
C.
isIconicIn
Indicates that something is widely recognized as a defining or emblematic example within a particular context, domain, or location.
-
D.
iconicView
Indicates that one entity provides a famous, widely recognized, or symbolically important visual perspective of another entity.
-
E.
designedToBeIconicLandmark
Indicates that something was intentionally created or planned to serve as a visually distinctive, memorable landmark or symbol.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:14 a.m.