Triple
T30921234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alcoa Highway |
E787727
|
entity |
| Predicate | isPrimaryConnectorBetween |
P77852
|
FINISHED |
| Object | Alcoa and Knoxville |
—
|
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: Alcoa and Knoxville | Statement: [Alcoa Highway, isPrimaryConnectorBetween, Alcoa and Knoxville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryConnectorBetween Context triple: [Alcoa Highway, isPrimaryConnectorBetween, Alcoa and Knoxville]
-
A.
isScenicConnectorBetween
Indicates that something serves as a visually appealing route or link connecting two locations or entities.
-
B.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
isShortConnector
Indicates that one entity functions as a connector or link between other entities and is characterized by having a short length or duration.
-
E.
isMajorConnectorFor
chosen
Indicates that one entity serves as a primary or critical linkage or pathway connecting other entities within a system or network.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 29, 2026, 8:51 p.m.