Triple
T13581335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cole Hauser |
E324423
|
entity |
| Predicate | characteristicRole |
P59266
|
FINISHED |
| Object | tough characters |
—
|
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: tough characters | Statement: [Cole Hauser, characteristicRole, tough characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicRole Context triple: [Cole Hauser, characteristicRole, tough characters]
-
A.
roleCharacteristic
chosen
Indicates that a particular characteristic, quality, or attribute is associated with and helps define a given role or function.
-
B.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
C.
designedRole
Indicates that one entity has been created, configured, or intended to serve a particular function, purpose, or role in relation to another entity.
-
D.
speakerRole
Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
-
E.
cultRole
Indicates that an entity holds a specific role, position, or function within a cult or cult-like group.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb031e8048190a5f2ea934308036c |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.