Triple
T16938793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessean |
E410895
|
entity |
| Predicate | geographicEndpoint |
P14201
|
FINISHED |
| Object | U.S. capital region |
—
|
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: U.S. capital region | Statement: [Tennessean, geographicEndpoint, U.S. capital region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicEndpoint Context triple: [Tennessean, geographicEndpoint, U.S. capital region]
-
A.
endpointRegion
chosen
Indicates that one entity serves as the geographic or logical region in which the other entity’s endpoint is located or configured.
-
B.
hasEndpointCity
Indicates that a route, connection, or path terminates at a particular city as one of its endpoints.
-
C.
geographicStrategy
Indicates a relationship where an entity’s actions, plans, or policies are organized or guided according to geographic factors such as location, region, or spatial distribution.
-
D.
geographicReception
Indicates the geographic area or location where something (such as a work, message, or signal) is received, experienced, or has effect.
-
E.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2b88bc8190aeb7b07032478ae3 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.