Triple
T37718821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super-Patriot |
E939526
|
entity |
| Predicate | hasSuccessorIdentity |
P202246
|
FINISHED |
| Object | U.S. Agent |
—
|
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: U.S. Agent | Statement: [Super-Patriot, hasSuccessorIdentity, U.S. Agent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorIdentity Context triple: [Super-Patriot, hasSuccessorIdentity, U.S. Agent]
-
A.
hasSuccessorUsers
Indicates that one user or set of users is followed or replaced by another user or set of users in a sequence or succession.
-
B.
hasOnlineSuccessor
Indicates that one entity is the direct online or digital successor of another, typically replacing or continuing its function in an online context.
-
C.
hasSuccessorLeader
Indicates that one leader directly follows another in a position of authority or leadership role.
-
D.
hasSuccessorNames
Indicates that an entity is followed or replaced by one or more entities identified as its successors.
-
E.
hasSuccessors
Indicates that an entity is followed or replaced by one or more subsequent entities in a sequence, process, or lineage.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0064f8efa48190956287f548a8057d |
completed | May 10, 2026, 10:59 a.m. |
| PD | Predicate disambiguation | batch_6a006471e75c8190adae99bd75e7411b |
completed | May 10, 2026, 10:56 a.m. |
| PDg | Predicate description generation | batch_6a0064f8496081908ac3bb4c53ed08aa |
completed | May 10, 2026, 10:59 a.m. |
Created at: May 3, 2026, 4:18 p.m.