Triple
T5091687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crakers |
E114764
|
entity |
| Predicate | centralCharacterRelation |
P37304
|
FINISHED |
| Object | closely associated with Snowman |
—
|
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: closely associated with Snowman | Statement: [Crakers, centralCharacterRelation, closely associated with Snowman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralCharacterRelation Context triple: [Crakers, centralCharacterRelation, closely associated with Snowman]
-
A.
relationshipToCharacter
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
B.
relatedCharacter
chosen
Indicates that one character has a specified relationship or association with another character.
-
C.
characterActorRelationship
Indicates a relationship where an actor portrays or is associated with a specific character in a work.
-
D.
fictionalRelationship
Indicates a relationship that exists only within a fictional or imagined context between entities.
-
E.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7541b2bc8190b58c2a23733b7825 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.