Triple
T4507015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Road Runner High Speed Online |
E101352
|
entity |
| Predicate | contention |
P57067
|
FINISHED |
| Object | shared neighborhood bandwidth |
—
|
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: shared neighborhood bandwidth | Statement: [Road Runner High Speed Online, contention, shared neighborhood bandwidth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contention Context triple: [Road Runner High Speed Online, contention, shared neighborhood bandwidth]
-
A.
controversy
Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
petition
Indicates that one entity formally requests or appeals to another entity, typically an authority, for a specific action or change.
-
D.
capitalContested
Indicates that the status of being the capital of a region or country is disputed or claimed by multiple parties.
-
E.
controlContested
Indicates that authority or dominance over something is disputed or challenged between two or more parties.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd570e7bb8819097f7a575384a10a8 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:01 p.m.