Triple

T27488450
Position Surface form Disambiguated ID Type / Status
Subject Port Royal State Historic Park E693809 entity
Predicate hasNearbyWaterbody P8567 FINISHED
Object Red River
The Red River is a tributary of the Cumberland River in Tennessee, known for flowing through historic areas such as near Port Royal State Historic Park.
E1350908 NE 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: Red River | Statement: [Port Royal State Historic Park, hasNearbyWaterbody, Red River]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Red River
Triple: [Port Royal State Historic Park, hasNearbyWaterbody, Red River]
Generated description
The Red River is a tributary of the Cumberland River in Tennessee, known for flowing through historic areas such as near Port Royal State Historic Park.

Provenance (5 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_69ef5382b9648190be0b1ef2ad5d043c completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62e8720a481908e9bc6e74631df4b completed May 2, 2026, 5:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12d0bb49e88190972a6a6dfb457482 completed May 24, 2026, 10:19 a.m.
NEDg Description generation batch_6a12d234d9448190934052fbbf66e999 completed May 24, 2026, 10:25 a.m.
NED2 Entity disambiguation (via description) batch_6a12d2c4f3788190bb09cedbf1c29be3 completed May 24, 2026, 10:28 a.m.
Created at: April 27, 2026, 1:03 p.m.