Triple
T33775572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liam Stewart |
E865505
|
entity |
| Predicate | isPowerful |
P177678
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Liam Stewart, isPowerful, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPowerful Context triple: [Liam Stewart, isPowerful, true]
-
A.
hasPowerful
Indicates that one entity possesses significant strength, influence, or capability relative to another entity or context.
-
B.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
wasPowerfulIn
Indicates that an entity possessed significant power, influence, or effectiveness within a specified domain, context, or time period.
-
D.
isPowerhouseIn
Indicates that an entity is a dominant, highly influential, or leading force within a specified domain, context, or location.
-
E.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:45 a.m.