Triple
T3453371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exsurge Domine |
E72843
|
entity |
| Predicate | deadlineDuration |
P8693
|
FINISHED |
| Object | 60 days from publication in Germany |
—
|
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: 60 days from publication in Germany | Statement: [Exsurge Domine, deadlineDuration, 60 days from publication in Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deadlineDuration Context triple: [Exsurge Domine, deadlineDuration, 60 days from publication in Germany]
-
A.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
B.
possibleDuration
Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
-
C.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
D.
durationDependsOn
Indicates that the length of time of one event or state is determined or influenced by another event, condition, or factor.
-
E.
durationUntil
chosen
Indicates the length of time remaining from a given starting point until a specified future event or state occurs.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbaa457fc8190824ca00254e962f9 |
completed | March 8, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.