Triple
T27391456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etienne Guibourg |
E691543
|
entity |
| Predicate | allegedAssociateOf |
P120587
|
FINISHED |
| Object | Catherine Monvoisin |
—
|
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: Catherine Monvoisin | Statement: [Etienne Guibourg, allegedAssociateOf, Catherine Monvoisin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedAssociateOf Context triple: [Etienne Guibourg, allegedAssociateOf, Catherine Monvoisin]
-
A.
allegedAgentOf
Indicates that one entity is claimed or suspected, but not confirmed, to be the agent responsible for an action or event involving another entity.
-
B.
hasAllegedRelationshipWith
chosen
Indicates a claimed or suspected relationship between two entities that is not confirmed as factual.
-
C.
allegesCollaborationWith
Indicates that one party claims or asserts that another party has worked together or cooperated with a specified entity.
-
D.
allegedOrganization
Indicates that an entity is claimed or suspected to be an organization, without confirming that the claim is true.
-
E.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 12:26 p.m.