Triple
T4186714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secretary of State of Puerto Rico |
E88329
|
entity |
| Predicate | lineOfSuccessionTo |
P656
|
FINISHED |
| Object | Governor of Puerto Rico |
—
|
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: Governor of Puerto Rico | Statement: [Secretary of State of Puerto Rico, lineOfSuccessionTo, Governor of Puerto Rico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineOfSuccessionTo Context triple: [Secretary of State of Puerto Rico, lineOfSuccessionTo, Governor of Puerto Rico]
-
A.
monarchSuccessor
Indicates that one monarch directly follows another in a royal line of succession.
-
B.
dateOfSuccession
Indicates the specific date on which one entity formally succeeded or took over a role, position, or title from another.
-
C.
successorDynasty
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
D.
successionOrder
chosen
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
E.
succeededToThroneBy
Indicates that one ruler or monarch is followed in succession by another who takes over the throne.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.