Triple
T36625999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Party Secretary of Bijie |
E904169
|
entity |
| Predicate | relativePowerComparedToMayor |
P204975
|
FINISHED |
| Object | higher |
—
|
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: higher | Statement: [Party Secretary of Bijie, relativePowerComparedToMayor, higher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePowerComparedToMayor Context triple: [Party Secretary of Bijie, relativePowerComparedToMayor, higher]
-
A.
underMayor
Indicates that one entity holds a position, role, or responsibility that is subordinate to or overseen by a mayor.
-
B.
hasMunicipalMayorAsCounterpart
Indicates that one municipal mayor serves as the official counterpart or peer to another municipal mayor in a formal relationship or interaction.
-
C.
mayorRoleTypically
Indicates that the specified role or position is typically held by, or commonly associated with, a mayor.
-
D.
mayorResponsibleFor
Indicates that a mayor holds responsibility or authority over a specified task, decision, area, or issue.
-
E.
numberOfTermsAsMayor
Indicates the number of distinct terms an individual has served in the role of mayor.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.