Triple
T30648478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Banks |
E780187
|
entity |
| Predicate | catchCharacteristic |
P128001
|
FINISHED |
| Object | raising his voice when angry |
—
|
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: raising his voice when angry | Statement: [Philip Banks, catchCharacteristic, raising his voice when angry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catchCharacteristic Context triple: [Philip Banks, catchCharacteristic, raising his voice when angry]
-
A.
tailCharacteristic
Indicates that an entity possesses a particular property, feature, or quality specifically related to its tail.
-
B.
castCharacteristic
Indicates that a particular characteristic or attribute is associated with, or defines, a cast or group of performers.
-
C.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
D.
entityCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
E.
capturesCharacter
Indicates that one entity seizes, traps, or takes control of another character.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a9537fc819083849c707a8add46 |
completed | May 2, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:30 p.m.