Triple
T17606048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decree Frequens |
E428833
|
entity |
| Predicate | timeBetweenCouncilsSpecified |
P1678
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Decree Frequens, timeBetweenCouncilsSpecified, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeBetweenCouncilsSpecified Context triple: [Decree Frequens, timeBetweenCouncilsSpecified, yes]
-
A.
councilHeldBetween
Indicates that a council, meeting, or formal deliberative session was held involving the two specified entities as participating parties.
-
B.
termLength
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
C.
legislativePeriodicity
chosen
Indicates how frequently a legislative body or process recurs or is scheduled to occur over time.
-
D.
securityCouncilMandateRenewalFrequency
Indicates how often a United Nations Security Council mandate is renewed or extended over time.
-
E.
timeFromProposalToRatification
Indicates the duration of time that passes between when a proposal is made and when it is formally ratified.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4c06a88190a0be2dec3d6056c4 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.