Triple
T6548865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pemuda Pancasila |
E151077
|
entity |
| Predicate | claimsToUphold |
P12796
|
FINISHED |
| Object | state ideology Pancasila |
—
|
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: state ideology Pancasila | Statement: [Pemuda Pancasila, claimsToUphold, state ideology Pancasila]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsToUphold Context triple: [Pemuda Pancasila, claimsToUphold, state ideology Pancasila]
-
A.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
B.
claimsToMark
Indicates that one entity asserts or alleges that it has marked, labeled, or designated another entity in some specified way.
-
C.
claimMethod
Indicates the method or procedure by which a claim is made, submitted, or executed.
-
D.
claimsToContinue
Indicates that one entity asserts or promises that an action, state, or relationship will persist into the future.
-
E.
claimsToFollow
chosen
Indicates that one entity asserts or professes adherence to the principles, rules, or leadership 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.