Triple
T10042797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese constitutionalism |
E205335
|
entity |
| Predicate | hasDebateTerm |
P91795
|
FINISHED |
| Object | xianzheng (宪政) |
—
|
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: xianzheng (宪政) | Statement: [Chinese constitutionalism, hasDebateTerm, xianzheng (宪政)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDebateTerm Context triple: [Chinese constitutionalism, hasDebateTerm, xianzheng (宪政)]
-
A.
hasDebate
Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
-
B.
hasLongTermDebateOn
Indicates that there is an ongoing, extended period of discussion, disagreement, or argument concerning a particular topic or issue.
-
C.
hasDebatedPerson
Indicates that one person has engaged in a debate or formal argumentative discussion with another person.
-
D.
canDebate
Indicates that one entity has the ability or permission to engage in a debate or argumentative discussion with another entity.
-
E.
debatedAs
Indicates that one entity is discussed or argued over in terms of being equivalent to, or serving in the role of, another entity within a debate or comparative argument.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf60a2208190846e57b5f5649307 |
completed | April 2, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:55 p.m.