Triple
T19210462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andromaque |
E480342
|
entity |
| Predicate | reçoit |
P4382
|
FINISHED |
| Object | accueil critique favorable à sa création |
—
|
LITERAL FINISHED |
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: accueil critique favorable à sa création | Statement: [Andromaque, reçoit, accueil critique favorable à sa création]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reçoit Context triple: [Andromaque, reçoit, accueil critique favorable à sa création]
-
A.
receives
chosen
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
B.
recipientOf
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
C.
reception
Indicates the act of receiving or welcoming someone or something, often marking the initial acknowledgment or acceptance in an interaction or process.
-
D.
reaches
Indicates that one entity extends or moves until it makes contact with, attains, or arrives at another entity or point.
-
E.
receivedFor
Indicates that something was obtained, accepted, or taken into possession on behalf of or for the benefit of a specified entity.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f9a0d1248190953e36e44f0cafdd |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:21 p.m.