Triple
T30804434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyck |
E784458
|
entity |
| Predicate | historicalStateBefore1918 |
P129965
|
FINISHED |
| Object | Kingdom of Prussia |
—
|
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: Kingdom of Prussia | Statement: [Lyck, historicalStateBefore1918, Kingdom of Prussia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalStateBefore1918 Context triple: [Lyck, historicalStateBefore1918, Kingdom of Prussia]
-
A.
statusBefore1918
Indicates that a particular status, condition, or classification applied to an entity prior to the year 1918.
-
B.
regionBefore1945
Indicates that one region existed or was defined in a particular way prior to the year 1945.
-
C.
countryBefore1918
chosen
Indicates that one country existed or held a particular status prior to the year 1918 in relation to another country or temporal reference.
-
D.
countryBefore1940
Indicates that the specified country existed or was recognized as such prior to the year 1940.
-
E.
coordinateCountryBefore1945
Indicates that one country served as the coordinating or administratively responsible country for another (or for a territory) prior to the year 1945.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: April 29, 2026, 8:42 p.m.