Triple
T8280939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia State Route 300 |
E193668
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 300
SR 300 is a state highway in Georgia that serves as a key connector route in the southwestern part of the state.
|
E723290
|
NE FINISHED |
How this triple was built (4 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: SR 300 | Statement: [Georgia State Route 300, abbreviation, SR 300]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 300 Context triple: [Georgia State Route 300, abbreviation, SR 300]
-
A.
SR 200
SR 200 is a state highway in Florida that runs across the northeastern part of the state, connecting US 41 in Hernando to Fernandina Beach near the Atlantic coast.
-
B.
SR 400
SR 400 is a major north–south highway in Georgia that serves as a key commuter and traffic corridor through the Atlanta metropolitan area.
-
C.
SR 50
SR 50 is a major east–west state highway in Florida that runs across the central part of the state, connecting the Gulf Coast near Weeki Wachee to the Atlantic Coast at Titusville.
-
D.
SR 100
SR 100 is a state highway in Georgia that runs generally north–south, connecting several small towns and rural areas in the western part of the state.
-
E.
SR 100
SR 100 is a state highway designation commonly used in the United States for a numbered route within a state's road network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: SR 300 Triple: [Georgia State Route 300, abbreviation, SR 300]
Generated description
SR 300 is a state highway in Georgia that serves as a key connector route in the southwestern part of the state.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 300 Target entity description: SR 300 is a state highway in Georgia that serves as a key connector route in the southwestern part of the state.
-
A.
SR 200
SR 200 is a state highway in Florida that runs across the northeastern part of the state, connecting US 41 in Hernando to Fernandina Beach near the Atlantic coast.
-
B.
SR 400
SR 400 is a major north–south highway in Georgia that serves as a key commuter and traffic corridor through the Atlanta metropolitan area.
-
C.
SR 50
SR 50 is a major east–west state highway in Florida that runs across the central part of the state, connecting the Gulf Coast near Weeki Wachee to the Atlantic Coast at Titusville.
-
D.
SR 100
SR 100 is a state highway in Georgia that runs generally north–south, connecting several small towns and rural areas in the western part of the state.
-
E.
SR 100
SR 100 is a state highway designation commonly used in the United States for a numbered route within a state's road network.
- F. None of above. chosen
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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ee66e48190af7058b14f3daac9 |
completed | March 31, 2026, 7:38 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd686d9be081908b0490e708f51ad7 |
completed | April 1, 2026, 6:48 p.m. |
| NEDg | Description generation | batch_69cd6d5441248190a9e32281dc8e8d62 |
completed | April 1, 2026, 7:09 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cd7e20f71c8190959319c6683a2810 |
completed | April 1, 2026, 8:20 p.m. |
Created at: March 30, 2026, 5:51 p.m.