Triple
T34850925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 1 in South Carolina |
E1004597
|
entity |
| Predicate | entersStateFrom |
P12839
|
FINISHED |
| Object | Georgia |
—
|
NE NERFINISHED |
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: Georgia | Statement: [U.S. Route 1 in South Carolina, entersStateFrom, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entersStateFrom Context triple: [U.S. Route 1 in South Carolina, entersStateFrom, Georgia]
-
A.
entersFrom
chosen
Indicates that one entity moves into or arrives at a place, state, or context by coming from another specified source or location.
-
B.
exitsToState
Indicates that one state or condition transitions or leads directly to another specified state.
-
C.
alsoFromState
Indicates that two entities originate from, are associated with, or come from the same state or region.
-
D.
enteredIntoForceForInitialStates
Indicates that a legal agreement, treaty, or instrument has become legally binding and effective for the original group of states that first adopted or ratified it.
-
E.
transitionState
Indicates a change in condition or phase from one defined state to another within a process or system.
- 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4 p.m.