Triple
T24760026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheila and B. Devotion |
E619409
|
entity |
| Predicate | frontPersonRealName |
P9233
|
FINISHED |
| Object | Annie Chancel |
—
|
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: Annie Chancel | Statement: [Sheila and B. Devotion, frontPersonRealName, Annie Chancel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontPersonRealName Context triple: [Sheila and B. Devotion, frontPersonRealName, Annie Chancel]
-
A.
frontPerson
Indicates that one entity serves as the primary representative, leader, or public face positioned at the forefront in relation to another entity.
-
B.
realName
chosen
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
-
C.
fullNameRevealed
Indicates that an entity’s complete personal name has been disclosed or made known to another party or in a given context.
-
D.
hasFrontPerson
Indicates that an entity is represented, led, or fronted publicly by a specific person.
-
E.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:27 a.m.