Triple
T34513685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Angel |
E886090
|
entity |
| Predicate | communicatesWithCharacter |
P93257
|
FINISHED |
| Object | Prior Walter |
—
|
NE NERFINISHED |
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: Prior Walter | Statement: [The Angel, communicatesWithCharacter, Prior Walter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicatesWithCharacter Context triple: [The Angel, communicatesWithCharacter, Prior Walter]
-
A.
spokenToCharacter
chosen
Indicates that one character has verbally addressed or communicated directly with another character.
-
B.
collaboratesWithCharacter
Indicates that one character works together with another character toward a shared goal or activity.
-
C.
connectsCharacter
Indicates that one character is linked or associated with another in some meaningful way.
-
D.
communicatesTo
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
-
E.
communicationTrait
Indicates a characteristic or quality related to how an entity communicates or engages in communication.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 2:01 a.m.