Triple
T32644380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leakee |
E834560
|
entity |
| Predicate | followedByPersonaOf |
P196333
|
FINISHED |
| Object | Roman Reigns in NXT |
—
|
LITERAL FINISHED |
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: Roman Reigns in NXT | Statement: [Leakee, followedByPersonaOf, Roman Reigns in NXT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByPersonaOf Context triple: [Leakee, followedByPersonaOf, Roman Reigns in NXT]
-
A.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
B.
followedPerson
Indicates that one person has chosen to follow another person, typically to receive updates or track their activities.
-
C.
followsRelationshipOf
Indicates that one entity follows, succeeds, or comes after another in a sequence, order, or relational chain.
-
D.
followedByOnUS1
Indicates that one entity directly follows another on U.S. Route 1 (US1) in a sequence or ordering.
-
E.
calledToFollowBy
Indicates that one entity has been summoned, invited, or designated by another entity to follow, accompany, or pursue a path or role associated with that other entity.
- F. None of above. chosen
Provenance (4 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
| PDg | Predicate description generation | batch_69fe21afdc4c8190913ac4b55a9a5f52 |
completed | May 8, 2026, 5:47 p.m. |
Created at: May 1, 2026, 1:07 a.m.