Triple
T14273661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mandarin |
E353857
|
entity |
| Predicate | ringPower |
P113529
|
FINISHED |
| Object | ice generation |
—
|
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: ice generation | Statement: [The Mandarin, ringPower, ice generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ringPower Context triple: [The Mandarin, ringPower, ice generation]
-
A.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
B.
realPower
Indicates that an entity possesses genuine, effective control or influence over another entity or situation, beyond nominal or formal authority.
-
C.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
D.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
E.
keyPower
Indicates that an entity possesses a primary or controlling power, authority, or influence over another entity or process.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6582f5308190969f4cfd724d9139 |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:10 a.m.