Triple
T15774492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Crown |
E382451
|
entity |
| Predicate | finalPartitionDate |
P120277
|
FINISHED |
| Object | 1795 |
—
|
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: 1795 | Statement: [Polish Crown, finalPartitionDate, 1795]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalPartitionDate Context triple: [Polish Crown, finalPartitionDate, 1795]
-
A.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
B.
dateFinalized
Indicates that a specific date has been set as the official or final completion/confirmation time for an associated event, decision, or record.
-
C.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
D.
finalAppTransitionDate
Indicates the date on which the final transition or change of state for the application was completed.
-
E.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
- F. None of above. chosen
Provenance (4 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05198c1588190a65e23c18443eb5c |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.