Triple
T31245163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rutles |
E796667
|
entity |
| Predicate | fictionalMember |
P192373
|
FINISHED |
| Object | Ron Nasty |
—
|
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: Ron Nasty | Statement: [The Rutles, fictionalMember, Ron Nasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalMember Context triple: [The Rutles, fictionalMember, Ron Nasty]
-
A.
fictionalBandMember
chosen
Indicates that one entity is a member of a fictional or imaginary musical band associated with another entity.
-
B.
hasFictionalMember
Indicates that a group, organization, or collection includes at least one member that is fictional rather than real.
-
C.
fictionalMembersCount
Indicates the number of fictional entities that are members of a given group or collection.
-
D.
fictionalCharacter
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
-
E.
hasFictionalFamilyMember
Indicates that one entity has another entity as a family member within a fictional or imagined context.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 29, 2026, 9:11 p.m.