Triple
T14669888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electorate of Trier |
E344481
|
entity |
| Predicate | electorateSince |
P42150
|
FINISHED |
| Object | 1356 |
—
|
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: 1356 | Statement: [Electorate of Trier, electorateSince, 1356]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electorateSince Context triple: [Electorate of Trier, electorateSince, 1356]
-
A.
electorateUntil
Indicates that an entity serves as an electorate for another entity up to, but not beyond, a specified point in time.
-
B.
electorateFrom
Indicates that an electorate or voting body originates from, is drawn from, or is associated with a particular geographic area, jurisdiction, or population source.
-
C.
electorateEstablished
chosen
Indicates that an electorate or voting district has been formally created or brought into existence.
-
D.
electorateEstablishedBy
Indicates that an electorate (voting district or body of voters) was created or formally brought into existence by a specific authority, law, or founding action.
-
E.
electorate
Indicates that an entity functions as the body of people entitled to vote in relation to a particular political unit, office, or decision.
- 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54ef2908190b189ced65eec434a |
completed | April 14, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.