Triple
T18567576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROC Constitution |
E453793
|
entity |
| Predicate | subsequentAmendmentYears |
P28679
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [ROC Constitution, subsequentAmendmentYears, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentAmendmentYears Context triple: [ROC Constitution, subsequentAmendmentYears, 1992]
-
A.
amendmentYear
Indicates the year in which an amendment to a law, document, or agreement was formally made or enacted.
-
B.
majorAmendmentYear
chosen
Indicates the year in which a significant or major amendment was made to something (such as a document, law, or agreement).
-
C.
amendmentCount
Indicates the number of amendments that have been made to a given item, document, or entity.
-
D.
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.
-
E.
furtherAmendedBy
Indicates that an existing item (such as a document, law, or agreement) is modified again by a subsequent amendment, building on prior changes.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53affc3e08190b4d16b5ccb0bddbc |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.