Triple
T34982229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krenim |
E1008844
|
entity |
| Predicate | temporalWeaponPowerSource |
P61281
|
FINISHED |
| Object | temporal core |
—
|
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: temporal core | Statement: [Krenim, temporalWeaponPowerSource, temporal core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalWeaponPowerSource Context triple: [Krenim, temporalWeaponPowerSource, temporal core]
-
A.
hasEnergyWeapons
Indicates that an entity is equipped with or uses weapons that emit or manipulate energy (such as lasers or plasma) rather than conventional physical projectiles.
-
B.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
C.
heldTemporalPower
Indicates that an entity exercised governing or authoritative control over another entity or domain during a specific period of time.
-
D.
sourceOfPower
chosen
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
E.
specialWeapon
Indicates that an entity is a weapon with unique, enhanced, or otherwise exceptional properties compared to standard weapons.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.