Triple
T9893010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Silent Cry |
E181499
|
entity |
| Predicate | mainCharactersRelation |
P38921
|
FINISHED |
| Object | brothers |
—
|
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: brothers | Statement: [The Silent Cry, mainCharactersRelation, brothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharactersRelation Context triple: [The Silent Cry, mainCharactersRelation, brothers]
-
A.
relationshipToCharacter
chosen
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
B.
characterActorRelationship
Indicates a relationship where an actor portrays or is associated with a specific character in a work.
-
C.
basedOnCharactersRelationship
Indicates that something is determined or derived from the relationship between the characters involved.
-
D.
relatedCharacter
Indicates that one character has a specified relationship or association with another character.
-
E.
relatedCharacterContext
Indicates a contextual relationship between characters, such as roles, interactions, or situational connections that link them within a specific narrative or setting.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4814a3c8190ab1fd7f755a44508 |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.