Triple
T15644673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 監察院 |
E376147
|
entity |
| Predicate | establishedInConstitution |
P30578
|
FINISHED |
| Object | 1947年 |
—
|
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: 1947年 | Statement: [監察院, establishedInConstitution, 1947年]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedInConstitution Context triple: [監察院, establishedInConstitution, 1947年]
-
A.
isPartOfConstitution
Indicates that something forms a component or section within a constitution or constitutional document.
-
B.
citesConstitutionalProvision
Indicates that one legal document, decision, or argument explicitly references and relies on a specific provision of a constitution.
-
C.
recognizedInConstitution
chosen
Indicates that an entity’s status, rights, or role is formally acknowledged and defined within a constitution.
-
D.
constitutionalName
Indicates the official name of an entity as defined or recognized in its constitution or foundational legal document.
-
E.
identifiesCorrectConstitution
Indicates that an entity correctly determines, selects, or recognizes the appropriate constitution in a given context.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ed400ec8190a14a9f7cf3092865 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.