Triple
T24405809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lunatic Fringe |
E615307
|
entity |
| Predicate | linkedToRingName |
P87629
|
FINISHED |
| Object | Dean Ambrose |
—
|
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: Dean Ambrose | Statement: [The Lunatic Fringe, linkedToRingName, Dean Ambrose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToRingName Context triple: [The Lunatic Fringe, linkedToRingName, Dean Ambrose]
-
A.
hasRingName
chosen
Indicates that an entity is associated with, or designated by, a specific ring name.
-
B.
associatedWithRing
Indicates that an entity has a connection or relationship with a specific ring, such as ownership, membership, or involvement.
-
C.
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).
-
D.
originalRingName
Indicates the name originally used for a ring before any later changes or renamings.
-
E.
ringName
Indicates that a ring is identified or referred to by a specific name.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294dfd8d88190b831b6a8f4157980 |
completed | April 29, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.