Triple
T33683025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bird Dog |
E862950
|
entity |
| Predicate | hasRivalCharacterTrait |
P159938
|
FINISHED |
| Object | showing off |
—
|
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: showing off | Statement: [Bird Dog, hasRivalCharacterTrait, showing off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalCharacterTrait Context triple: [Bird Dog, hasRivalCharacterTrait, showing off]
-
A.
rivalryCharacterization
Indicates a relationship in which two entities are characterized as rivals, typically defined by ongoing competition, opposition, or conflict between them.
-
B.
rivalryCharacterizedBy
chosen
Indicates a relationship where a rivalry is defined or distinguished by a particular feature, quality, or circumstance.
-
C.
hasSupportingCharacterTrait
Indicates that a supporting character possesses a particular trait, quality, or characteristic.
-
D.
antagonistAttribute
Indicates that an entity possesses a characteristic or role specifically associated with being an antagonist in a narrative or conflict.
-
E.
rivalryFeature
Indicates a competitive or adversarial relationship between entities, often characterized by ongoing opposition or comparison.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 1:43 a.m.