Triple
T30865808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Je t'aime… moi non plus |
E786195
|
entity |
| Predicate | reRecordedWith |
P170577
|
FINISHED |
| Object | Jane Birkin |
—
|
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: Jane Birkin | Statement: [Je t'aime… moi non plus, reRecordedWith, Jane Birkin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reRecordedWith Context triple: [Je t'aime… moi non plus, reRecordedWith, Jane Birkin]
-
A.
recordedWith
Indicates that something was captured, documented, or produced using a particular tool, device, medium, or method.
-
B.
reRecordedFrom
Indicates that one recording is a new recording derived from, based on, or made again from an earlier recording.
-
C.
areRecordedBy
Indicates that an event, observation, or piece of information is captured or documented by a specific recording agent, device, or process.
-
D.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
-
E.
usedForRecordingBy
Indicates that something serves as a medium, tool, or device that is employed by an agent to make a recording.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691ac00448190b6b89a8c4cb0c9c0 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:47 p.m.