Triple
T25210252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nous finirons ensemble |
E631663
|
entity |
| Predicate | directorAlsoStarred |
P162869
|
FINISHED |
| Object | Guillaume Canet |
—
|
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: Guillaume Canet | Statement: [Nous finirons ensemble, directorAlsoStarred, Guillaume Canet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorAlsoStarred Context triple: [Nous finirons ensemble, directorAlsoStarred, Guillaume Canet]
-
A.
notableCastWorkedWith
Indicates that there is a notable professional collaboration or working relationship between members of a cast.
-
B.
hasSiblingCoStars
Indicates that two or more entities have appeared together as co-stars and are siblings in relation to each other.
-
C.
coDirectedWith
Indicates that two or more entities jointly directed the same work or project.
-
D.
directorSpouseInCast
Indicates that a film’s director is married to someone who appears as a cast member in that same film.
-
E.
laterFeaturedCastFrom
Indicates that one entity appears as a featured cast member in a later work, episode, or installment relative to another entity.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f62e83045c8190a424a2e401a88e9e |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d886828819080ec2f742b9449e3 |
completed | May 2, 2026, 4:59 p.m. |
Created at: April 21, 2026, 12:58 p.m.