Triple
T18845757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C8 |
E460907
|
entity |
| Predicate | hasSuccessorBodyName |
P133159
|
FINISHED |
| Object | C9 |
—
|
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: C9 | Statement: [C8, hasSuccessorBodyName, C9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorBodyName Context triple: [C8, hasSuccessorBodyName, C9]
-
A.
hasSuccessorUse
Indicates that one use or application of something is directly followed or replaced by another use in a sequence or progression.
-
B.
hasSuccessorTitleHolder
Indicates that one entity is the next title holder or office bearer succeeding another entity in a given position or title.
-
C.
hasMoreAggressiveSuccessor
Indicates that one entity is followed or replaced by another entity that exhibits a higher level of aggressiveness in behavior, strategy, or effect.
-
D.
hasOnlineSuccessor
Indicates that one entity is the direct online or digital successor of another, typically replacing or continuing its function in an online context.
-
E.
hasSuccessorSegment
Indicates that one segment directly follows another segment in a sequence or ordered structure.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ee96988190bf247b986777945c |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:56 a.m.