Triple
T5233370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Indonesia |
E118159
|
entity |
| Predicate | numberOfAmendmentRounds |
P1039
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Constitution of Indonesia, numberOfAmendmentRounds, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfAmendmentRounds Context triple: [Constitution of Indonesia, numberOfAmendmentRounds, 4]
-
A.
amendmentCount
chosen
Indicates the number of amendments that have been made to a given item, document, or entity.
-
B.
hasAmendments
Indicates that one entity (such as a document, law, or agreement) includes or is associated with one or more modifications, changes, or additions made after its original creation.
-
C.
amendmentMechanism
Indicates the process or rules by which an agreement, document, or system can be formally changed or updated.
-
D.
numberOfMajorRevisions
Indicates the count of significant revision events that have occurred for an entity.
-
E.
isAmendmentTo
Indicates that one item formally modifies, revises, or adds to the content or terms of another item.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b0389048190b55b7c44fe657044 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77bf1ef08190bb3487b3f3ee088c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.