Triple
T25509777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Aherne |
E639341
|
entity |
| Predicate | portrayedCharactersType |
P87723
|
FINISHED |
| Object | suave 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: suave characters | Statement: [Brian Aherne, portrayedCharactersType, suave characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedCharactersType Context triple: [Brian Aherne, portrayedCharactersType, suave characters]
-
A.
portrayedByCharacterType
chosen
Indicates that an entity is depicted or represented by a character of a specified type (e.g., hero, villain, sidekick) in a narrative or media work.
-
B.
portrayedVia
Indicates that one entity is represented, depicted, or expressed through a particular medium, method, or channel.
-
C.
depictsCharacterType
Indicates that one entity visually represents or portrays a character of a specified type or role.
-
D.
characterPortrayedIs
Indicates that one entity serves as the fictional or dramatic role that is depicted or played by another entity.
-
E.
portraysCharacterInGenre
Indicates that an entity depicts or plays a character within works belonging to a specified genre.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 2:48 p.m.