Triple
T28356110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KHOU-TV |
E718231
|
entity |
| Predicate | areaOfCoverage |
P136191
|
FINISHED |
| Object | Houston metropolitan area |
—
|
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 metropolitan area | Statement: [KHOU-TV, areaOfCoverage, Houston metropolitan area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaOfCoverage Context triple: [KHOU-TV, areaOfCoverage, Houston metropolitan area]
-
A.
hasAreaOfCoverage
chosen
Indicates that an entity provides services, influence, or applicability within a specified geographic or conceptual region.
-
B.
mayCoverArea
Indicates that one entity is permitted or able to extend over, include, or encompass a specified spatial area.
-
C.
fieldCovered
Indicates that a specified field or area is physically or functionally covered by some material, object, or condition.
-
D.
coveredArea
Indicates that one entity occupies or extends over a specific spatial region or surface area associated with another entity.
-
E.
hasProtectedAreaCoverage
Indicates that a specified portion or extent of an area falls within officially designated protected areas.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 12:49 a.m.