Triple
T21624156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casino de Beaulieu-sur-Mer |
E533653
|
entity |
| Predicate | styleCharacter |
P144821
|
FINISHED |
| Object | elegant |
—
|
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: elegant | Statement: [Casino de Beaulieu-sur-Mer, styleCharacter, elegant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleCharacter Context triple: [Casino de Beaulieu-sur-Mer, styleCharacter, elegant]
-
A.
characterStyle
Indicates how a character is visually or typographically presented, such as its font, weight, size, or decorative attributes.
-
B.
character3
Indicates a tertiary or additional character role associated with an entity, typically the third distinct character linked within a given context or work.
-
C.
character2
Indicates that a second character entity is involved in the relationship or context defined by the predicate.
-
D.
characterVisualStyle
Indicates the visual design or aesthetic style applied to a character, such as their overall look, art style, or graphical presentation.
-
E.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef521125f481909ccfc95d884976e2 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:34 p.m.