Triple
T5591570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Côtes du Rhône |
E146888
|
entity |
| Predicate | alsoProducedIn |
P46755
|
FINISHED |
| Object | Northern Rhône communes |
—
|
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: Northern Rhône communes | Statement: [Côtes du Rhône, alsoProducedIn, Northern Rhône communes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoProducedIn Context triple: [Côtes du Rhône, alsoProducedIn, Northern Rhône communes]
-
A.
coProduced
Indicates that two or more entities jointly produced or created a work, project, or product together.
-
B.
associatedProduction
chosen
Indicates that there is a related or connected production (such as a work, performance, or manufacturing process) linked to the subject entity.
-
C.
alsoPlayedIn
Indicates that an entity (such as a person or performer) participated or appeared in another work, production, or context in addition to the one already referenced.
-
D.
producedFilm
Indicates that one entity served as the producer (or production company) responsible for making or financing the creation of a particular film.
-
E.
laterProducedIn
Indicates that one production event or version occurred after another in time.
- 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020a3365c8190bd223226c0a6969f |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.