Triple
T33788406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madame St. Aubert |
E865860
|
entity |
| Predicate | protagonistOfSameWork |
P181008
|
FINISHED |
| Object | Emily St. Aubert |
—
|
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: Emily St. Aubert | Statement: [Madame St. Aubert, protagonistOfSameWork, Emily St. Aubert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistOfSameWork Context triple: [Madame St. Aubert, protagonistOfSameWork, Emily St. Aubert]
-
A.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
B.
hasAuthorOfSameWorkAs
Indicates that two authors are related by having written or contributed to the same work.
-
C.
sameFictionalPersonAs
Indicates that two entities represent the same fictional character, even if they appear in different works, versions, or contexts.
-
D.
attestedInWorksOf
Indicates that something (such as a claim, form, or usage) is documented or evidenced within the works produced by a particular author or creator.
-
E.
workBySameAuthorAs
Indicates that two works share the same author, i.e., they were created by the same person or 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_69f3498ecc2c8190bcd85e3f11dc215e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: May 1, 2026, 1:45 a.m.