Triple
T19648040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zelda Fuller |
E471731
|
entity |
| Predicate | talkative |
P83331
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zelda Fuller, talkative, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: talkative Context triple: [Zelda Fuller, talkative, true]
-
A.
communicationTrait
chosen
Indicates a characteristic or quality related to how an entity communicates or engages in communication.
-
B.
dialogue
Indicates that two or more entities are engaged in an exchange of spoken or written communication with each other.
-
C.
alsoSpeak
Indicates that an entity, in addition to another language or mode of communication already mentioned, speaks this additional language or communicates in this additional way.
-
D.
typicalSpeaker
Indicates that the subject is a prototypical or characteristic speaker or source of utterances in the context of the object.
-
E.
dialogueType
Indicates the specific kind or category of dialogue occurring between entities (e.g., question-answer, negotiation, instruction).
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64126cea88190a1a6929f46de4686 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.