Triple
T14499228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Bank |
E359586
|
entity |
| Predicate | isSettingForCharacter |
P78408
|
FINISHED |
| Object | Rat |
—
|
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: Rat | Statement: [River Bank, isSettingForCharacter, Rat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSettingForCharacter Context triple: [River Bank, isSettingForCharacter, Rat]
-
A.
isCharacterInSetting
chosen
Indicates that a particular character appears or exists within a specified setting or environment.
-
B.
isPivotalForCharacter
Indicates that something plays a crucial, defining role in shaping a character’s development, decisions, or narrative arc.
-
C.
definesStateCharacter
Indicates that something specifies or determines the essential qualities or characteristics of a state or condition.
-
D.
characterSetting
Indicates that a character is associated with, appears in, or is situated within a particular setting or environment.
-
E.
usesCharacter
Indicates that one entity employs, incorporates, or relies on a particular character (such as a symbol, letter, or persona) in its form, function, or representation.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9311cc748190880c784f173b7f2b |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.