Triple
T4375830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston Ship Channel |
E99003
|
entity |
| Predicate | openedToDeepDraftTraffic |
P46304
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [Houston Ship Channel, openedToDeepDraftTraffic, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToDeepDraftTraffic Context triple: [Houston Ship Channel, openedToDeepDraftTraffic, 1914]
-
A.
supportsDrafts
Indicates that an entity is capable of handling, saving, or working with draft versions of items before they are finalized.
-
B.
openedToGoodsTraffic
chosen
Indicates that a route, facility, or infrastructure was officially made available for the movement and handling of goods or freight traffic.
-
C.
openedRouteThrough
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
-
D.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
E.
hasDraft
Indicates that one entity possesses or is associated with a preliminary or unfinished version of 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3523d4e888190b4367ed6aa17d463 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.