Triple
T3067022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Falconer |
E62125
|
entity |
| Predicate | hasInnerMonologue |
P17543
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [George Falconer, hasInnerMonologue, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInnerMonologue Context triple: [George Falconer, hasInnerMonologue, yes]
-
A.
canBeThoughtBy
chosen
Indicates that something is capable of being conceived, imagined, or mentally represented by a thinking entity.
-
B.
hasProseDialogue
Indicates that one entity contains or features spoken or conversational content expressed in prose form involving another entity.
-
C.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
D.
hasEnigmaticCharacter
Indicates that something possesses a mysterious, puzzling, or difficult-to-interpret quality or nature.
-
E.
hasMetafictionalRole
Indicates that an entity plays a role within a story that self-consciously comments on, references, or breaks the conventions of fiction itself.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada0fd87308190918e7b616f033faa |
completed | March 8, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.