Triple
T23927489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Eddy |
E602395
|
entity |
| Predicate | successorInEngagement |
P36906
|
FINISHED |
| Object | George V |
—
|
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: George V | Statement: [Prince Eddy, successorInEngagement, George V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInEngagement Context triple: [Prince Eddy, successorInEngagement, George V]
-
A.
successorAct
Indicates that one action or event directly follows and replaces another in a sequence or process.
-
B.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another entity.
-
C.
successorReceives
Indicates that a successor entity obtains or is granted something (such as rights, assets, or responsibilities) from a predecessor.
-
D.
successorRole
chosen
Indicates that one role or position directly follows and replaces another in a sequence or organizational structure.
-
E.
successorInPractice
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1e13e8819096432b8133c7d71e |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:49 p.m.