Triple
T29383132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OHR |
E745184
|
entity |
| Predicate | powersKnownAs |
P177147
|
FINISHED |
| Object | Bonn Powers |
—
|
NE NERFINISHED |
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: Bonn Powers | Statement: [OHR, powersKnownAs, Bonn Powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powersKnownAs Context triple: [OHR, powersKnownAs, Bonn Powers]
-
A.
powersType
Indicates that one entity has a specific type or category of power or ability in relation to another entity.
-
B.
kingPowers
Indicates that an entity possesses the legal or authoritative powers associated with a king over another entity or domain.
-
C.
powers
Indicates that one entity supplies or provides the energy, authority, or driving force that enables another entity to function or operate.
-
D.
recognizedPower
Indicates that one entity formally acknowledges and accepts another entity’s authority, influence, or control as legitimate.
-
E.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 28, 2026, 2:36 p.m.