Triple
T29017039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Valentine |
E737339
|
entity |
| Predicate | hasSuccessorRoleIn |
P36906
|
FINISHED |
| Object | Valentine Pontifex |
—
|
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: Valentine Pontifex | Statement: [Lord Valentine, hasSuccessorRoleIn, Valentine Pontifex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuccessorRoleIn Context triple: [Lord Valentine, hasSuccessorRoleIn, Valentine Pontifex]
-
A.
hasPredecessorRoleIn
Indicates that one role functioned earlier in time or sequence relative to another role within the same context or position.
-
B.
successorInSomeRoles
Indicates that one entity has taken over or followed another entity in certain specified roles or positions.
-
C.
successorRole
chosen
Indicates that one role or position directly follows and replaces another in a sequence or organizational structure.
-
D.
successorStateRole
Indicates that one role represents the state or position that directly follows and replaces another role in a sequence or process.
-
E.
hasRoleInSuccession
Indicates that an entity holds a specific role or position within a defined line or order of succession.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 28, 2026, 9:46 a.m.