Triple
T37275730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houston–San Antonio |
E924640
|
entity |
| Predicate | connectsLargestCityInState |
P201227
|
FINISHED |
| Object | Houston |
—
|
NE NERFINISHED |
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: Houston | Statement: [Houston–San Antonio, connectsLargestCityInState, Houston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsLargestCityInState Context triple: [Houston–San Antonio, connectsLargestCityInState, Houston]
-
A.
connectsMajorCityState
Indicates that something serves as a link or route between a major city and the state it belongs to.
-
B.
connectsLargestCitiesOf
Indicates a relationship where something (typically a route, network, or infrastructure) links together the largest cities within a specified region or set.
-
C.
capitalCityOfAssociatedState
Indicates that a city serves as the capital of the state with which another entity is associated.
-
D.
isLargestCityIn
Indicates that one city has the greatest population or size compared to all other cities within a specified region or administrative area.
-
E.
largestCity
Indicates that one city is the most populous or significant urban center within a specified region or entity.
- F. None of above. chosen
Provenance (4 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
| PDg | Predicate description generation | batch_69ffdf46e18c8190a5e4f4e5211cb087 |
completed | May 10, 2026, 1:28 a.m. |
Created at: May 3, 2026, 4:16 p.m.