Triple
T35670740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nusantara |
E1030708
|
entity |
| Predicate | capitalMoveApprovalDate |
P14303
|
FINISHED |
| Object | 2022-01-18 |
—
|
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: 2022-01-18 | Statement: [Nusantara, capitalMoveApprovalDate, 2022-01-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalMoveApprovalDate Context triple: [Nusantara, capitalMoveApprovalDate, 2022-01-18]
-
A.
approvalDate
chosen
Indicates the date on which an action, request, or item was formally approved.
-
B.
mandateConfirmedDate
Indicates the date on which a mandate (such as an authorization or directive) was formally confirmed or validated.
-
C.
dateOfTransfer
Indicates the specific date on which a transfer of something (such as ownership, rights, or funds) from one party to another takes place.
-
D.
dateChangeApprovedBy
Indicates that a proposed change to a date (such as a deadline, event date, or schedule) has been formally reviewed and approved by a specific party.
-
E.
finalAppTransitionDate
Indicates the date on which the final transition or change of state for the application was completed.
- 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:05 p.m.