Triple
T17897210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Road Runner |
E447459
|
entity |
| Predicate | offeredOver |
P129222
|
FINISHED |
| Object | cable television infrastructure |
—
|
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: cable television infrastructure | Statement: [Road Runner, offeredOver, cable television infrastructure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredOver Context triple: [Road Runner, offeredOver, cable television infrastructure]
-
A.
offering
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
-
B.
offeredIn
Indicates that something is made available or provided within a particular context, setting, or medium.
-
C.
hasOffering
Indicates that one entity provides, presents, or makes available an offering (such as a product, service, or item) to another entity or context.
-
D.
offeredService
Indicates that one entity has provided or made available a service to another entity.
-
E.
offersServiceIn
Indicates that a provider makes a particular service available within a specified location or jurisdiction.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d8045748190a4e8c4684439a96b |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:19 a.m.