Triple
T26700746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruce Nolan |
E673147
|
entity |
| Predicate | laterUsesPowersFor |
P100686
|
FINISHED |
| Object | helping others |
—
|
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: helping others | Statement: [Bruce Nolan, laterUsesPowersFor, helping others]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterUsesPowersFor Context triple: [Bruce Nolan, laterUsesPowersFor, helping others]
-
A.
usesPowerFor
chosen
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
B.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
-
C.
enhancesPowersOf
Indicates that one entity increases, amplifies, or strengthens the abilities or powers of another entity.
-
D.
invokesPower
Indicates that one entity calls upon, activates, or makes use of the power, authority, or special ability associated with another entity.
-
E.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 3:31 a.m.