Triple
T19467096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Côte Brune |
E487027
|
entity |
| Predicate | relativeStyleToCôteBlonde |
P8654
|
FINISHED |
| Object | more structured |
—
|
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: more structured | Statement: [Côte Brune, relativeStyleToCôteBlonde, more structured]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeStyleToCôteBlonde Context triple: [Côte Brune, relativeStyleToCôteBlonde, more structured]
-
A.
inTheStyleOf
Indicates that one entity is created, performed, or presented in a manner that imitates or closely resembles the characteristic style of another entity.
-
B.
relatedStyle
chosen
Indicates that one style is associated with, similar to, or derived from another style in some relevant way.
-
C.
broughtStyleTo
Indicates that one entity introduced or contributed a particular style or aesthetic to another entity or context.
-
D.
FrenchSide
Indicates that an entity is positioned on, associated with, or belongs to the French side of a border, division, or relationship.
-
E.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e2aee081908330a5665fa60482 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.