Triple
T349652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German–Polish Non-Aggression Pact |
E7413
|
entity |
| Predicate | initialDuration |
P8729
|
FINISHED |
| Object | 10 years |
—
|
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: 10 years | Statement: [German–Polish Non-Aggression Pact, initialDuration, 10 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialDuration Context triple: [German–Polish Non-Aggression Pact, initialDuration, 10 years]
-
A.
durationUntil
Indicates the length of time remaining from a given starting point until a specified future event or state occurs.
-
B.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
C.
hasOfficialDuration
chosen
Indicates the formally defined length of time associated with an event, process, or entity.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
startDate
Indicates the point in time when an event, state, or relationship begins.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb1dc5f88190b54d084c6def7fc5 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.