Triple
T7469243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frackville, Pennsylvania |
E176462
|
entity |
| Predicate | transportationJunction |
P36754
|
FINISHED |
| Object | near Interstate 81 |
—
|
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: near Interstate 81 | Statement: [Frackville, Pennsylvania, transportationJunction, near Interstate 81]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationJunction Context triple: [Frackville, Pennsylvania, transportationJunction, near Interstate 81]
-
A.
transportationJunctionFor
chosen
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
-
B.
transportationFacility
Indicates that one entity is a facility or location used for the transportation or transit of people or goods in relation to another entity.
-
C.
transportHubType
Indicates the specific category or kind of transport hub associated with an entity (e.g., airport, train station, bus terminal).
-
D.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
E.
transportNetwork
Indicates a relationship where infrastructure or services enable the movement of people or goods between different locations.
- 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_69c69f223fd88190b4c69b95d7cbeeda |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3f845e081908117783ff1e63e23 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:41 p.m.