Triple
T22020930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The River |
E543843
|
entity |
| Predicate | hasIntimateStory |
P11859
|
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: [The River, hasIntimateStory, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntimateStory Context triple: [The River, hasIntimateStory, true]
-
A.
hasInfluentialStory
Indicates that one entity possesses or is associated with a story that significantly shapes, impacts, or guides the beliefs, actions, or development of another entity.
-
B.
isStoried
Indicates that something has a rich history, reputation, or legacy built up over time, often marked by notable events or traditions.
-
C.
hasNarrative
chosen
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
D.
hasRomanticMisadventures
Indicates that an entity experiences a series of problematic, comical, or unsuccessful romantic relationships or encounters.
-
E.
hasMoreIntimateProductionStyle
Indicates that one entity’s production style is comparatively more intimate, personal, or close-up than another’s.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c7b3308190ac056bef6f82722e |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:23 p.m.