Triple
T37668095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beany and Cecil |
E937875
|
entity |
| Predicate | characterTraitOfCecil |
P37384
|
FINISHED |
| Object | seasick sea serpent |
—
|
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: seasick sea serpent | Statement: [Beany and Cecil, characterTraitOfCecil, seasick sea serpent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterTraitOfCecil Context triple: [Beany and Cecil, characterTraitOfCecil, seasick sea serpent]
-
A.
secondaryCharacterTrait
Indicates that a secondary or supporting character possesses a particular attribute, quality, or personality trait.
-
B.
associatedCharacterTrait
chosen
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
-
C.
notableLeaderTrait
Indicates that the specified trait is a particularly prominent or defining characteristic of the leader in question.
-
D.
childCharacterTrait
Indicates that a child possesses or exhibits a particular character trait.
-
E.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fff86e544c81908063f61b876c9d78 |
completed | May 10, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fff7e7cb688190977eeca41aad25b9 |
completed | May 10, 2026, 3:13 a.m. |
Created at: May 3, 2026, 4:18 p.m.