Triple
T29106843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weiqi |
E736783
|
entity |
| Predicate | hasBalancingMechanism |
P8166
|
FINISHED |
| Object | komi |
—
|
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: komi | Statement: [Weiqi, hasBalancingMechanism, komi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBalancingMechanism Context triple: [Weiqi, hasBalancingMechanism, komi]
-
A.
hasCheckAndBalanceWith
Indicates that two entities mutually monitor, limit, or counterbalance each other's powers or actions to prevent dominance or abuse.
-
B.
providesCounterbalanceTo
Indicates that one entity serves to offset, balance, or mitigate the effects, influence, or force of another entity.
-
C.
requiresBalancing
Indicates that one entity or action depends on being offset, equalized, or counteracted by another to maintain a required equilibrium or fairness.
-
D.
hasMechanism
chosen
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
E.
hasCounterweightType
Indicates that an entity is associated with or uses a specific type or category of counterweight.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 11:16 a.m.