Triple
T33683008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bird Dog |
E862950
|
entity |
| Predicate | describesCharacterRole |
P192169
|
FINISHED |
| Object | romantic rival |
—
|
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: romantic rival | Statement: [Bird Dog, describesCharacterRole, romantic rival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesCharacterRole Context triple: [Bird Dog, describesCharacterRole, romantic rival]
-
A.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
B.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
C.
describesCharactersIn
Indicates that one entity provides a description or account of the characters that appear in another entity.
-
D.
characterInWorkDescribedAs
Indicates that a character is portrayed or described in a particular way within a specific work.
-
E.
depictsPersonRole
Indicates that an image or representation shows a person in a specific role, function, or capacity.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: May 1, 2026, 1:43 a.m.