Triple
T5674410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy and Great Council |
E125050
|
entity |
| Predicate | plannedSince |
P4691
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Holy and Great Council, plannedSince, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedSince Context triple: [Holy and Great Council, plannedSince, 1961]
-
A.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
B.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
C.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
D.
datePlanned
chosen
Indicates that a specific date has been scheduled or intended for a particular event, action, or relationship to occur.
-
E.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
- 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_69c008295c808190acfe78915e7d656a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025303860819093e51f176babed71 |
completed | March 22, 2026, 5:21 p.m. |
| PD | Predicate disambiguation | batch_69c021bc3894819084f37d14ba4b2644 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.