Triple
T6780164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bung Hatta |
E155658
|
entity |
| Predicate | coProclaimed |
P72780
|
FINISHED |
| Object | Indonesian independence |
—
|
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: Indonesian independence | Statement: [Bung Hatta, coProclaimed, Indonesian independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coProclaimed Context triple: [Bung Hatta, coProclaimed, Indonesian independence]
-
A.
proclaimedFrom
Indicates that something was formally announced or declared originating from a particular source, place, or authority.
-
B.
reproclaimed
Indicates that something was proclaimed or announced again, typically reaffirming or restating a previous declaration.
-
C.
wasProclaimed
Indicates that an entity was formally announced, declared, or made official, typically through an authoritative or ceremonial proclamation.
-
D.
canBeProclaimedUnder
Indicates that something is eligible or authorized to be formally declared or announced under a specified law, authority, or framework.
-
E.
coIntroduced
Indicates that two or more entities jointly introduced or presented something together for the first time.
- F. None of above. chosen
Provenance (4 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26b32c0819093f86b1002260660 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d182213c819086fcbbfd3d64d80b |
completed | March 27, 2026, 6:50 p.m. |
Created at: March 27, 2026, 2:14 p.m.