Triple
T37300930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston–Dallas |
E925937
|
entity |
| Predicate | hasProposedService |
P6787
|
FINISHED |
| Object | high-speed rail |
—
|
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: high-speed rail | Statement: [Houston–Dallas, hasProposedService, high-speed rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProposedService Context triple: [Houston–Dallas, hasProposedService, high-speed rail]
-
A.
hasProposed
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
-
B.
hasServiceTo
chosen
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
C.
hasProposal
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
-
D.
hasProposedRole
Indicates that one entity has suggested or put forward a specific role or position for another entity.
-
E.
hasProposedRate
Indicates that one entity has put forward or suggested a specific rate or price to another entity.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.