Triple
T12884758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Floss |
E308196
|
entity |
| Predicate | hasTypeInNarrative |
P107444
|
FINISHED |
| Object | rural river |
—
|
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: rural river | Statement: [River Floss, hasTypeInNarrative, rural river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeInNarrative Context triple: [River Floss, hasTypeInNarrative, rural river]
-
A.
hasPartInNarrative
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
-
B.
hasAliasInNarrative
Indicates that an entity is referred to by an alternative name or alias within a specific narrative or story context.
-
C.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
D.
hasNarrativeRole
Indicates that an entity participates in a narrative with a specific functional role (e.g., protagonist, antagonist, narrator) relative to the story.
-
E.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
- F. None of above. chosen
Provenance (4 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d97c7d0598819080cab0a2314bc106 |
completed | April 10, 2026, 10:41 p.m. |
Created at: April 9, 2026, 5:39 p.m.