Triple
T18851330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PT |
E461046
|
entity |
| Predicate | cameToFederalPowerIn |
P8145
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [PT, cameToFederalPowerIn, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameToFederalPowerIn Context triple: [PT, cameToFederalPowerIn, 2003]
-
A.
cameToPowerIn
chosen
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
B.
cameToPowerThrough
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
-
C.
effectOnFederalPower
Indicates how an action, decision, or condition changes, limits, or expands the authority or powers of the federal government.
-
D.
cameToPowerWithSupportFrom
Indicates that an entity attained a position of power or authority aided or enabled by the backing, assistance, or endorsement of another entity.
-
E.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05995e88190b189864fcbda68e5 |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.