Triple
T31482340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean de Brienne |
E803178
|
entity |
| Predicate | partnerInPasDeDeuxWith |
P34738
|
FINISHED |
| Object | Raymonda |
—
|
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: Raymonda | Statement: [Jean de Brienne, partnerInPasDeDeuxWith, Raymonda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInPasDeDeuxWith Context triple: [Jean de Brienne, partnerInPasDeDeuxWith, Raymonda]
-
A.
dancePartner
chosen
Indicates that two entities are engaged in or paired together for a dance.
-
B.
hasDoublesPartner
Indicates that one entity serves as the doubles partner of another in a paired or team-based activity or sport.
-
C.
partnerInEndingWith
Indicates that an entity participates as a partner in an event, process, or relationship that concludes with a specified outcome or terminal state.
-
D.
partnerInLoveTeam
Indicates that two entities are teammates who are also partners in a romantic or love-based relationship.
-
E.
partnerInUnionWith
Indicates a mutual partnership or union relationship between two entities, such as a civil, domestic, or similar legally or socially recognized union.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 30, 2026, 9:33 p.m.