Triple
T35670743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nusantara |
E1030708
|
entity |
| Predicate | plannedFullCompletion |
P133759
|
FINISHED |
| Object | 2045 |
—
|
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: 2045 | Statement: [Nusantara, plannedFullCompletion, 2045]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedFullCompletion Context triple: [Nusantara, plannedFullCompletion, 2045]
-
A.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
B.
originalCompletionDate
Indicates the date on which something was first completed, before any subsequent changes, revisions, or updates.
-
C.
completionOf
Indicates that one entity represents the finished state, fulfillment, or successful conclusion of another entity, process, or requirement.
-
D.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
E.
plannedOperationUntil
chosen
Indicates that an operation is scheduled or intended to continue up to a specified end time or condition.
- 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_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:05 p.m.