Triple
T27235416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Loop |
E682257
|
entity |
| Predicate | mayConnectTo |
P845
|
FINISHED |
| Object | other state highways |
—
|
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: other state highways | Statement: [State Loop, mayConnectTo, other state highways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayConnectTo Context triple: [State Loop, mayConnectTo, other state highways]
-
A.
connectsTo
chosen
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
-
C.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
D.
notConnectedBy
Indicates that there is no direct link, path, or relationship connecting the referenced entities.
-
E.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 9:47 a.m.