Triple
T35809038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RK-Bro |
E1035178
|
entity |
| Predicate | hasRingNameOfMember |
P87629
|
FINISHED |
| Object | Riddle |
—
|
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: Riddle | Statement: [RK-Bro, hasRingNameOfMember, Riddle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRingNameOfMember Context triple: [RK-Bro, hasRingNameOfMember, Riddle]
-
A.
hasRingName
chosen
Indicates that an entity is associated with, or designated by, a specific ring name.
-
B.
ringNameOf
Indicates that one entity is the name or designation assigned to a particular ring (such as a ring structure, ring system, or ring object).
-
C.
hasRingPersonaType
Indicates that an entity’s type or role is defined specifically in the context of its ring-related persona or identity.
-
D.
hasRing
Indicates that one entity possesses, wears, or is characterized by the presence of a ring.
-
E.
originalRingName
Indicates the name originally used for a ring before any later changes or renamings.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 3, 2026, 4:06 p.m.