Triple
T23723936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cirque de Cilaos |
E586217
|
entity |
| Predicate | siblingCirque |
P363
|
FINISHED |
| Object | Cirque de Mafate |
—
|
NE NERFINISHED |
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: Cirque de Mafate | Statement: [Cirque de Cilaos, siblingCirque, Cirque de Mafate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siblingCirque Context triple: [Cirque de Cilaos, siblingCirque, Cirque de Mafate]
-
A.
sisterShow
Indicates that two shows are related as sister shows, typically sharing common origins, networks, or production ties without one being derived from the other.
-
B.
sisterTheatre
Indicates that two theatres are formally associated as sister venues, typically collaborating or sharing resources while remaining distinct entities.
-
C.
sibling
chosen
Indicates that two entities share at least one parent, making them brothers or sisters to each other.
-
D.
siblingRival
Indicates a relationship where two siblings are in competition or conflict with each other.
-
E.
sisterVenue
Indicates that two venues are related as peers or counterparts, typically sharing ownership, branding, or affiliation without one being subordinate to the other.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b91364208190b3404534a7403e08 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:07 p.m.