Triple
T1276690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Assembly of South Korea |
E27229
|
entity |
| Predicate | budgetApprovalDeadline |
P8546
|
FINISHED |
| Object | before the start of the fiscal year |
—
|
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: before the start of the fiscal year | Statement: [National Assembly of South Korea, budgetApprovalDeadline, before the start of the fiscal year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetApprovalDeadline Context triple: [National Assembly of South Korea, budgetApprovalDeadline, before the start of the fiscal year]
-
A.
approvalDate
Indicates the date on which an action, request, or item was formally approved.
-
B.
hasDeadline
chosen
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
C.
budgetApprovalRequiredFor
Indicates that obtaining approval for a budget is a necessary prerequisite for proceeding with the associated entity or activity.
-
D.
proposalDate
Indicates the date on which a proposal is formally made or submitted from one entity to another.
-
E.
dateOfUltimatum
Indicates the specific date on which an ultimatum was issued, delivered, or came into effect in the relationship between the involved parties.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.