Triple
T28430982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dame Edna’s Hollywood |
E715126
|
entity |
| Predicate | hasHostRealName |
P69377
|
FINISHED |
| Object | Barry Humphries |
—
|
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: Barry Humphries | Statement: [Dame Edna’s Hollywood, hasHostRealName, Barry Humphries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHostRealName Context triple: [Dame Edna’s Hollywood, hasHostRealName, Barry Humphries]
-
A.
hasMainHost
Indicates that one entity serves as the primary or principal host for another entity.
-
B.
notRealNameOf
Indicates that the referenced name is not the entity’s actual or official name (e.g., it is false, fabricated, or otherwise not the real name of that entity).
-
C.
hostFullName
chosen
Indicates that one entity is the complete personal name (including given and family names, and possibly middle names or titles) of the host associated with another entity.
-
D.
hasNotableHost
Indicates that an entity is associated with a host who is particularly prominent, famous, or otherwise noteworthy.
-
E.
realName
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.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 1:39 a.m.